Stop Asking 'What % Have I Been To?' Until You Pick the Definition

TL;DR: "% of the world you've been to" is garbage until you define three things: what counts as a place, what counts as "been to," and what counts as "the world." Pick a denominator (193, 195, or territories), pick rules (layovers/overnights/transit), then compute Visited ÷ Total × 100 and publish your method.

Most people aren't bad at math.

They're bad at definitions.

Your travel percentage isn't one number. It's a data model.

Before you calculate anything, choose:

1. What counts as a place? (countries, territories, land area, population)

2. What counts as "been to"? (transit, day trip, overnight, "meaningful time")

3. What counts as "the world"? (UN members, UN + observers, sovereign states + territories)

If you and someone else don't match on those three choices, your percentages aren't comparable.

They're vibes with decimals.

The fastest way: pick a definition you can defend in one sentence

Use this formula:

Percent visited = (Visited units ÷ Total units) × 100

The formula is trivial. The hard part is choosing your unit (what you're counting) and your rule set (what "counts").

Unit = the thing you count. Example: "countries" or "territories."

Been to = the rule that turns a trip into yes/no. Example: "spent at least one night."

World = the master list you're measuring against. Example: "193 UN member states."

Pick all three. Your number stops being fake.

Pick one of these definitions (fast + defensible)

These are "drop-in calculators." Choose one, count your visited items, divide by the denominator.

Option A: UN member states (193) — easiest and most common

Definition: "Countries" = the 193 UN member states.

Compute: (# UN member states you count as visited / 193) × 100

Why it works: Stable denominator. Widely recognized. Easy to find lists.

Trade-off: Excludes observer states (which some people consider "countries").

Option B: UN members + observer states (195) — still simple

Definition: "Countries" = 193 UN members + 2 UN observer states (Holy See, Palestine) = 195.

Compute: (# visited / 195) × 100

Why it works: Captures the "195" number people quote. Still stable.

Trade-off: You still haven't decided what to do with territories.

Option C: Sovereign states + territories — maximalist, but list-dependent

Definition: "Places" = sovereign states plus dependent territories/overseas regions (e.g., Greenland, Puerto Rico).

Compute: (# visited states+territories / total items in your chosen master list) × 100

Why it works: Better matches how people actually travel (territories are real places with real airports).

Caution: The total varies by source list. If you don't publish your list, your number is un-auditable.

Define "been to" in one sentence

Your percentage only means what your rule set says it means.

A defensible default rule set (clean, strict, easy):

• Transit-only does not count
• Airport layover counts only if you leave the airport
• Day trips count only if you leave the airport/train station zone and spend real time in-country
• Overnight is the default "yes" (one night anywhere outside the airport)
• Cruise stops count only if you spend meaningful time off-ship (your call: e.g., 4+ hours)

You're not trying to impress anyone. You're trying to make the metric non-idiotic.

Copy/paste: disclose your method so your number is comparable

If you share your percent without your method, people can't compare it.

Use this template:

"I calculate % of world visited as [DENOMINATOR] visited / [TOTAL], counting a place as visited if [BEEN-TO RULE]. Transit-only doesn't count."

Example:

"I calculate % of world visited as UN member states visited / 193, counting a country visited if I spent at least one night outside the airport in that country."

Now your number is auditable.

Why different apps give different percentages

Because they silently pick different denominators and rules, then pretend it's the same metric.

Common hidden differences:

• One app uses 193 (UN members), another uses 195
• One app counts territories separately, another folds them into the sovereign state
• One app counts airport layovers, another doesn't
• One app treats Hong Kong separately, another counts it as China

Without a published definition, the app's percentage is a black box.

Edge cases that break comparisons

Disputed or partially recognized states

Pick a list and stick to it.

Examples that trigger fights: Taiwan, Kosovo, Western Sahara, Palestine.

Practical options:

• If you want stability: use UN 193 or UN 195 and accept what that implies
• If you want maximal realism: use a territories/states list and publish the source

Overseas territories

They can count separately, but only if you say so.

Examples: Puerto Rico, Greenland, Hong Kong.

Two clean approaches:

• Fold them in: Puerto Rico counts as "USA" only
• Separate them: Puerto Rico counts as its own "place"

Just don't do it inconsistently.

Schengen trips with no passport stamps

No stamp doesn't mean "not visited."

If your rule depends on stamps, it breaks inside Schengen and with modern e-gates.

Use a rule based on physical presence, not paperwork.

FAQ

What's the correct number of countries—195 or 193?

Both are "correct" under different definitions: 193 = UN member states; 195 = UN members + 2 observer states.

Do airport layovers count?

Not by default. The clean rule: it counts only if you leave the airport.

Does passing through on a train/bus count?

It can, but you decide. A strict rule requires overnight; a looser rule counts "entered the country and spent time outside a transit hub."

Do I have to stay overnight?

No, but overnight is the simplest defensible threshold. It prevents the metric from being dominated by layovers and drive-throughs.

How do I handle territories like Puerto Rico, Hong Kong?

Choose whether territories are separate units or folded into sovereign states, then stay consistent. If you count them separately, publish your master list.

Can I compare my number to other people's?

Only if you both match on (1) denominator, (2) unit definition, and (3) "been to" rules. If any differ, you're comparing different metrics.

The founder parallel: your day needs definition too

Founders make the same mistake with calls.

They say "I miss too many calls" or "everything is urgent," without defining what "urgent" means.

SmartLine is the definition-first fix: you get an AI-powered phone assistant that screens every inbound call, extracts the who/why/urgency, and sends you clean summaries so you decide what deserves attention.

Not more calls. A clear rule set for interruption.

Just like your travel percentage needs clear rules to mean anything, your phone needs smart filtering to protect your focus. SmartLine's AI assistant handles the screening so you only engage with calls that matter.

If you want a non-meaningless number, do this now

1. Pick UN 193 or UN 195 (unless you explicitly want territories)

2. Pick one "been to" rule (overnight is cleanest)

3. Compute Visited ÷ Total × 100

4. Publish your one-sentence method disclosure

Same formula. Better definition. A number you can defend.