That '% of World Visited' Number Is Fiction Until You Pick Your Formula

That "% of the world visited" number only becomes real after you declare two things: what counts as visited (numerator) and what counts as the world (denominator). If you visited 40 places, you can be at 20.7% (40/193), 20.5% (40/195), or 16.1% (40/249) depending on the list. The disagreement is not a bug. It is the math.

The only formula that matters: numerator ÷ denominator

Every tool that shows "% of the world visited" is doing this:

% visited = Visited units / Total units on a chosen list × 100

Two apps can both be "correct" and still disagree because they:

• Use a different denominator list (UN vs ISO vs a custom scratch map list)
• Use a different definition of visited (layovers count or not, territories separate or not)
• Use a different geo dataset to decide what country a GPS point belongs to

DaysAround makes this explicit. You pick the rules and the list, then we compute the result from your existing photos on-device. No accounts. No uploads. No shared map.

The numerator problem: what does "visited" mean?

"Visited" is not a universal concept. Most tools hide their rulebook, so you only see the final percentage.

The common "visited" rules that change your count

These choices explain why your numerator differs between apps:

• Layover rule
  • Strict: airport-only does not count
  • Loose: any landing counts
• Transit rule
  • Strict: you must stop for a meaningful visit
  • Loose: a border crossing or day trip counts
• Territory rule
  • Count territories separately (Puerto Rico is its own unit)
  • Roll territories into the sovereign state (Puerto Rico counts as USA)
• Disputed areas rule
  • Follow UN recognition
  • Follow ISO codes
  • Follow "if I entered and spent time there"

DaysAround reconstructs your visited list from photo GPS + timestamp metadata you already have. Then you review edge cases (airport-only photos, border towns) instead of trusting a black box.

The denominator problem: there is no single "world" list

People argue about whether the world has 193, 195, 197, or 249 "countries" because they are using different denominators.

The denominators people actually use (pick one)

Here are the only lists that matter in real life:

Denominator option	Total units	What it includes	Who it's for
UN member states	193	UN members only	People who mean "sovereign countries" in the common sense
UN members + UN observer states	195	Adds Vatican City and Palestine	People who want the most common "country count" variant
ISO 3166-1	249	Countries + territories + special areas	People who want territories to count distinctly (and accept a lower %)
Custom list	Varies	Your choices for disputed areas, Antarctica, microstates, territories	People who want a definition they can defend

DaysAround treats the denominator as a setting, not a political statement. Your percentage becomes: "X of Y on this list." That is the only honest way to share it.

A quick math example: why your % can drop overnight

Assume you visited 40 UN member states. Your travel did not change. Only the denominator changed.

• UN 193: 40 / 193 = 20.7%
• UN 195: 40 / 195 = 20.5%
• ISO 249: 40 / 249 = 16.1%

This is why one app says 21% and another says 16%.

The usual suspects: edge cases that swing the percentage

Most disagreement comes from a small set of special cases.

Territories and dependencies (the biggest swing)

If a tool uses ISO 3166-1 or a territory-heavy list, your denominator jumps fast.

Examples that are often counted separately:

• Greenland, Faroe Islands
• Hong Kong, Macao
• Puerto Rico, Guam
• Aruba, Curaçao

Why tools disagree: some apps count these as their own units. Others roll them into Denmark, China, the United States, or the Netherlands.

DaysAround lets you choose whether to track countries only, countries + territories, or your own list. This fits both "brag stats" and compliance-style tracking.

Microstates (often omitted, always arbitrary)

Microstates cause awkward mismatches because they are fully sovereign but easy to forget.

Common microstates:

• Vatican City, Monaco, San Marino, Liechtenstein, Andorra
• Nauru, Tuvalu

Why tools disagree: casual lists or scratch maps sometimes omit them. UN-based lists include them.

DaysAround photo-based reconstruction catches these trips if you took even a few geotagged photos there. If you did not, you can manually add them and keep the same denominator.

Disputed or partially recognized places (politics leaks into the math)

Examples:

• Kosovo, Taiwan, Palestine, Western Sahara
• Northern Cyprus, Somaliland, Crimea (status varies by dataset and recognition)

Why tools disagree:

• Some follow UN membership
• Some follow ISO codes
• Some hardcode their own decisions
• Some draw borders differently depending on map provider

DaysAround does not force a single worldview. You can use a UN-style denominator for easy comparison, then maintain a private custom list for your personal definition. This is the only way to make the number both comparable and defensible.

Antarctica (not a country, but many people want it to "count")

Antarctica is governed under the Antarctic Treaty System. It is not a sovereign state.

Why tools disagree:

• Some exclude it entirely
• Some count it as a territory-like unit
• Some show it only as a continent metric

DaysAround: if you want Antarctica to count, that is a custom-denominator choice. The key is to state it: "I include Antarctica as its own unit."

Why two tools disagree even if they claim the same list

Even if two apps both say "UN list," your number can still differ.

The most common technical causes

• Different geo datasets (Natural Earth vs OpenStreetMap vs proprietary)
• Different border geometry (especially around disputed areas and coastlines)
• Different point-in-polygon matching for GPS/photo points near borders
• Different rounding rules (20.7% shown as 21% vs 20%)

Because your data stays on-device with DaysAround, we show you the underlying visited units and let you correct edge cases instead of hiding them behind a single percentage. If something looks wrong, you fix the input list or a visit, not your trust.

"My rules, my list": a personal standard you can defend

If you want a percentage that is honest, write a 2 to 3 line definition you can repeat.

A simple checklist for your personal standard

1. Layovers: Do airport-only stops count? (Yes or no)
2. Territories: Count separately, or roll into the sovereign state?
3. Disputed areas: Follow UN membership, ISO, or your own policy?
4. Antarctica: Exclude, include, or track separately as a bonus?
5. Evidence: Self-report only, or evidence-based from photos?

Copy-paste definition templates

Choose one and keep it consistent.

Template A (easy comparison)

• "I count UN member states only (193). A country counts if I left the airport and spent time there."

Template B (includes observers)

• "I count UN members + observers (195). No airport-only layovers. Territories do not count separately."

Template C (territory-heavy traveler)

• "I use ISO 3166-1 (249). Territories count separately. Airport-only layovers do not count."

Template D (custom and explicit)

• "I use a custom list: UN 195 + Kosovo + Taiwan + Antarctica. I count day trips but not airport-only stops."

DaysAround supports this mindset: the goal is not a magical "correct" number. The goal is a number with stated assumptions, computed privately.

How to calculate "% of the world visited" without uploading travel history

You can calculate it privately in two ways. Both avoid the usual trap: giving a cloud app your full location history.

Method 1: Offline checklist + chosen denominator

This is the lowest-tech approach.

1. Pick a denominator list (UN 193, UN 195, ISO 249, or custom).
2. Mark visited units on a local checklist.
3. Compute: visited / total × 100.

This works, but it fails the way spreadsheets fail: you fall behind, you forget edge cases, and you lose confidence.

DaysAround reduces this manual burden by generating your visited list from your photo library through on-device photo metadata analysis, then letting you adjust the few tricky cases.

Method 2: On-device photo metadata scan (evidence-based, private)

If your phone has years of geotagged photos, you already have a travel log.

1. Scan your camera roll for GPS coordinates + timestamps.
2. Convert coordinates into visited units on your chosen list.
3. Review edge cases (airports, border towns, missing GPS).
4. Compute your percentage as "X of Y."

This is exactly what DaysAround is designed for:

• On-device photo metadata analysis only
• No cloud sync
• No analytics
• No accounts
• Your travel history never becomes someone else's database

If you care about legal and financial consequences, this same private travel history also supports compliance tracking like Schengen day counts using our Schengen Zone Calculator Tool.

How to share your number without lying (or oversharing)

The honest format is:

"X/Y on [List], using [Rules]."

Examples:

• "40/193 UN members, no airport-only layovers."
• "40/249 ISO list, territories count separately."
• "52/custom list, includes Kosovo and Taiwan, excludes airport-only stops."

DaysAround makes this easy because your denominator is explicit and your computation stays private. You can share the stat without sharing your location timeline.

FAQ: % of the world visited

What is the correct number of countries in the world?

There is no single correct number because "country" is not a single list. The most common baselines are 193 (UN members) and 195 (UN members + observers). 249 (ISO 3166-1) is not "countries" in the everyday sense. It includes territories and special areas.

Why does App A say I visited 18% but App B says 14%?

They are using different denominators, different "visited" rules, or different geo datasets. The biggest cause is UN 193 vs ISO 249.

Do territories count? If I visited Puerto Rico, did I visit the USA?

Some lists count Puerto Rico separately. Others roll it into the United States. Neither is "wrong." You need to choose a territory rule and denominator that match your intent.

Do layovers count as visiting?

Only if you decide they do. Many travelers use a strict rule: airport-only does not count. If you care about comparability with friends, write the rule down.

Does Antarctica count toward "world visited"?

Antarctica is not a sovereign country. Some people track it separately or include it in a custom denominator. The key is to declare your choice.

How should I handle disputed places like Kosovo, Taiwan, or Palestine?

Pick a policy and be consistent. Common policies are: follow UN membership, follow ISO codes, or use a custom list based on your own definition of "visited."

Can I create my own rules and still compare with friends?

Yes. Use two numbers: one on a common denominator (like UN 193 or 195) for comparison, and one on your custom list for personal meaning.

How can I calculate this without uploading my travel history?

Use an offline checklist, or use an on-device method that reads evidence locally. DaysAround does this by analyzing photo metadata on your iPhone so your travel history never leaves your device.

Can I compute it from my photo library only?

Yes, if your photos have GPS and timestamps. DaysAround reconstructs visited places from that metadata on-device, then you can fill gaps manually where you did not take photos.

Why do some tools change my percentage after an update?

They may have changed their denominator list, their border dataset, or their map matching logic. If the tool does not show the list and rules, you cannot audit the change.