Why Your '% of World Visited' Doesn't Match Your Friends' (It's the Denominator)

Your "% of the world visited" is never about your travel. It's about math: (places you count as visited) ÷ (total places the calculator thinks exist).

Two apps can look at the same trip history and output different percentages because they use different master lists (193 vs 195 vs 249 vs 330+) and different rules for territories, disputed regions, and Antarctica.

With DaysAround, you can run the same audit privately. Your travel history is reconstructed on-device from photo metadata. No uploads. No web calculators.

The equation everyone ignores

"Percent of the world visited" sounds objective. It is not.

Most tools are not measuring "the world." They are measuring a list.

• If you visited 30 sovereign countries:
  • 30/193 = 15.5% (UN members)
  • 30/195 = 15.4% (UN members + observers)
  • 30/249 = 12.0% (ISO 3166-1)

Same travel. Different denominator. Different percent.

DaysAround reconstructs your history from your photos, then lets you control how it's counted. The number stays consistent year to year because you control the rules.

The main denominator lists (and why they disagree)

If an app doesn't tell you which list it uses, treat the number as worthless. You can't reproduce it.

UN member states (193)

This is the cleanest "countries only" baseline.

• Pros: stable, widely understood, avoids territory debates
• Cons: excludes two common "country list" entries

UN members + observers (195)

This is the popular "195 countries" list.

• 193 UN members
• plus Vatican City and Palestine

It differs from 193 by only 2 entries. Rarely explains large gaps, but often explains "why are we off by 1 or 2?" conversations.

Travel-site "countries" lists (197-200+)

Many travel sites publish a "countries" list that includes partially recognized states.

Common add-ons:

• Kosovo
• Taiwan
• Western Sahara (varies)

Pros: matches travelers' intuitive idea of "places" Cons: political edge cases differ by editor

ISO 3166-1 (249)

ISO 3166-1 includes many territories and special areas.

• Pros: well-defined, widely used in software
• Cons: feels "too big" if you think "country = sovereign state"

This is where people see big percentage drops. If your friend's app uses ISO-style counting and yours uses UN 193, you "lose" several percentage points overnight.

"Country + territory" lists (250-330+)

These go beyond ISO and split out more places:

• Overseas territories (more granular)
• Sometimes constituent countries (England/Scotland/Wales/Northern Ireland)
• Sometimes Antarctica

Pros: rewarding if you travel widely through territories Cons: huge variance between lists

The conflict zones that break agreement

Most mismatches come from these categories:

Territories and dependencies (biggest swing)

Examples that often count as separate "places":

• Greenland
• Puerto Rico
• Guadeloupe, Martinique, Réunion
• Aruba, Curaçao
• Faroe Islands
• Gibraltar
• Hong Kong, Macau

If one app counts these separately and another rolls them into the sovereign state, both your numerator and denominator change.

Disputed regions (awkward swing)

Common disagreements:

• Kosovo
• Taiwan
• Palestine
• Western Sahara
• Northern Cyprus
• Somaliland

Two apps can both be "right" relative to their list. The key is disclosure and control.

Special regimes

These cause quiet mismatches:

• Hong Kong and Macau: separate "places" or part of China?
• England/Scotland/Wales/Northern Ireland: separate or part of UK?
• Kingdom of Denmark: Denmark vs Greenland vs Faroe Islands?

Antarctica (breaks everything)

Antarctica has no permanent population and isn't a sovereign country.

Apps handle it as:

• excluded entirely
• counted as a continent
• counted as a territory-like entry

If your friend's app counts Antarctica and yours doesn't, you can differ even if you took the same cruise.

Same travel, different percentages: three examples

Below are three hypothetical travelers. Each has one travel history run through common rule sets.

Rule sets for comparison

Preset	What it represents	Denominator
UN-193	UN member states	193
UN-195	UN members + observers	195
ISO-249	ISO 3166-1 style list	249
Territory-heavy	country + territory list	330

Traveler A: Europe weekender (sovereign-heavy)

Profile: mostly sovereign states, plus Vatican

• Visited sovereign states: 22
• Also visited: Vatican City
• Territories: none
• Total places: 23

Rule set	What counts	Percent
UN-193	22 (Vatican not in 193)	11.4%
UN-195	23 (includes Vatican)	11.8%
ISO-249	23	9.2%
Territory-heavy	23	7.0%

Traveler A barely changed their numerator, but the denominator moved dramatically.

Traveler B: Territory collector

Profile: fewer sovereign states, lots of territories

• Visited sovereign states: 14
• Visited territories: 12 (Puerto Rico, Aruba, Curaçao, Guadeloupe, Martinique, Réunion, Faroe Islands, Gibraltar, Hong Kong, Macau, etc.)
• Total places: 26

Rule set	What counts	Percent
UN-193	14 sovereign only	7.3%
UN-195	14 sovereign only	7.2%
ISO-249	26 (territories included)	10.4%
Territory-heavy	26	7.9%

Under UN-style counting, Traveler B "looks" less traveled than A. Under ISO-style counting, B jumps ahead. Neither is more correct.

Traveler C: Edge cases (disputed + Antarctica)

Profile: visited places that datasets treat differently

• Visited sovereign states: 20
• Visited disputed/partially recognized: 4 (Kosovo, Taiwan, Palestine, Western Sahara)
• Visited Antarctica: 1 cruise landing
• Total places: 25

Rule set	What counts	Percent
UN-193	20 (excludes disputed + Antarctica)	10.4%
UN-195	21 (adds Palestine only)	10.8%
ISO-249	~25 depending on ISO entries	10.0%
Territory-heavy	25 (if list includes all)	7.6%

Your numerator can change even when your denominator stays fixed, purely because the app's list doesn't recognize a region.

Settings audit checklist: debug any app in 5 minutes

1. Identify the master list

• Is this UN 193, UN 195, ISO 249, or custom?
• Does it show the full list somewhere?

If the list is hidden, you can't reproduce the result.

2. Check territory handling

• Are overseas territories separate entries or rolled into sovereign countries?
• What about Puerto Rico, Greenland, Hong Kong, Macau?

This is the biggest swing factor.

3. Check disputed regions

• Are Kosovo and Taiwan listed?
• Is Palestine included?
• Is Western Sahara included?

4. Check constituent-country splits

• Does UK count as 1, or do England/Scotland/Wales/Northern Ireland count separately?
• Are Denmark, Greenland, Faroe Islands split?

5. Check Antarctica handling

• Excluded? Counted as continent? Counted as place?

6. Check the "visited" rule

• Airport-only counts?
• Transit counts?
• Cruise stops count?
• Need overnight?

7. Check geocoding errors

• Does the app ever place you on wrong side of border?
• Does it label Saint Martin as France, Netherlands, or separate?

8. Confirm reproducibility

• Can you export your counted places?
• Can you save the rule set name for next year?

9. Check privacy and processing

• Do you upload location history or photos?
• Does the tool run on-device or in cloud?

DaysAround runs on-device on iOS. We don't upload your photo metadata or run analytics. You can compute your "% visited" and experiment with denominators without creating datasets on someone else's servers.

Pick a denominator you can keep for years

If you want your percentage to be useful, choose one you can stick to.

Sovereign-only (UN 193 or 195)

Choose this for:

• easy comparisons
• stable list
• fewer political edge cases

Sovereign + territories (ISO-249 style)

Choose this for:

• credit for territories you actually traveled to
• standards-based list

Custom traveler list

Choose this for:

• clear stance on Hong Kong, disputed regions
• optional Antarctica handling

The important part isn't which preset you pick. It's that you can explain and reproduce it.

DaysAround fits this model: scan your photos once, then compute stats under different denominators without redoing your travel log.

Compute privately without uploads

Many "percent of world visited" calculators require you to:

• create accounts
• upload location history
• accept hidden lists you can't audit

For digital nomads, that's a bad trade. Your travel pattern reveals visa compliance risk and tax exposure.

DaysAround uses the opposite workflow:

• Scan photo metadata on-device to reconstruct travel history
• Choose your denominator rules (countries vs territories, disputed regions, Antarctica)
• Get compliance-grade day counts alongside fun stats

Same data. Different denominators. You control the model. Your data never leaves your phone.