🗺 Your 48 hours in Tallinn on one map — save it.
👍4❤2🔥2

Channel
@amazingworldtravel
On this record: Topic · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Polls · Telegram's recommendations · Cite this entry
935,987subscribers
-164,650 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 316,228–1,000,000.
| Telegram ID | -1002178125373 |
|---|---|
| Type | Channel |
| Username | @amazingworldtravel |
| Description | This channel is about travelling the world and about how amazing our world is. |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 18 November 2026 |
| On Telegram | t.me/amazingworldtravel |
Travel — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Nov 2026, 01:38 | 935,987 | -4,123 |
| 15 Nov 2026, 02:01 | 940,110 | -5,443 |
| 11 Nov 2026, 21:49 | 945,553 | -2,073 |
| 9 Nov 2026, 22:39 | 947,626 | -2,465 |
| 8 Nov 2026, 10:38 | 950,091 | -2,669 |
| 7 Nov 2026, 03:30 | 952,760 | -911 |
| 6 Nov 2026, 04:11 | 953,671 | -1,651 |
| 5 Nov 2026, 06:49 | 955,322 | -1,701 |
| 4 Nov 2026, 05:39 | 957,023 | -1,545 |
| 3 Nov 2026, 03:15 | 958,568 | -1,469 |
| 2 Nov 2026, 03:37 | 960,037 | -1,631 |
| 1 Nov 2026, 04:59 | 961,668 | -1,995 |
| 31 Oct 2026, 03:15 | 963,663 | -1,467 |
| 30 Oct 2026, 02:29 | 965,130 | -1,434 |
| 28 Oct 2026, 23:56 | 966,564 | -2,254 |
| 27 Oct 2026, 21:16 | 968,818 | -1,418 |
| 26 Oct 2026, 21:07 | 970,236 | -1,164 |
| 25 Oct 2026, 22:30 | 971,400 | -1,257 |
| 24 Oct 2026, 20:50 | 972,657 | -1,617 |
| 23 Oct 2026, 17:57 | 974,274 | first reading |
212 posts held, back to 3 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 209 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 35 of 40 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 212 (3 August 2026 – 16 November 2026) |
| Views total | 60,694 |
| Reactions total | 127 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 01:51 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 66 of this channel’s own posts over the last 30 days: across 64 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 17 hours of being posted; a typical post has already reached 10.1% of its 24-hour view count within the first hour, and 47.8% within the first six; the median 24-hour reach across those posts is 806 views — 0.078% of this channel’s own subscriber count (90th percentile 849).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /136215 Sept 2026, 01:22 UTC | 203 minutes – 17 hours old | 693 views3 reactions | 60 minutes: 87 interp. → 3.0 hours: 203 → 6.0 hours: 372 interp. → 12 hours: 575still climbing at last reading | not yet at 24h | 5.5 hoursprovisional — final view count still climbing |
| /135915 Sept 2026, 01:22 UTC | 203 minutes – 17 hours old | 686 views5 reactions | 60 minutes: 87 interp. → 3.0 hours: 205 → 6.0 hours: 373 interp. → 12 hours: 571still climbing at last reading | not yet at 24h | 5.3 hoursprovisional — final view count still climbing |
| /135814 Sept 2026, 01:25 UTC | 4432 minutes – 41 hours old | 1,010 views ~no reaction reading | 60 minutes: 66 interp. → 3.0 hours: 190 → 6.0 hours: 366 → 12 hours: 578 → 24 hours: 781still climbing at last reading | 781measured | 9.7 hours |
| /135514 Sept 2026, 01:25 UTC | 4432 minutes – 41 hours old | 948 views2 reactions | 60 minutes: 67 interp. → 3.0 hours: 193 → 6.0 hours: 361 → 12 hours: 566 → 24 hours: 760still climbing at last reading | 760measured | 8.9 hours |
| /135413 Sept 2026, 01:24 UTC | 6063 minutes – 3 days old | 1,080 views ~no reaction reading | 3.0 hours: 150 → 6.0 hours: 324 → 12 hours: 540 → 24 hours: 725 → 2 days: 984still climbing at last reading | 725measured | 12 hours |
| /135113 Sept 2026, 01:24 UTC | 62under a minute – 3 days old | 1,080 views ~3 reactions | 60 minutes: 53 interp. → 3.0 hours: 148 → 6.0 hours: 323 → 12 hours: 536 → 24 hours: 720 → 2 days: 955still climbing at last reading | 720measured | 12 hours |
| /135012 Sept 2026, 01:16 UTC | 726 minutes – 4 days old | 1,150 views ~no reaction reading | 60 minutes: 57 → 3.0 hours: 146 → 6.0 hours: 336 → 12 hours: 564 → 24 hours: 754 → 2 days: 963still climbing at last reading | 754measured | 12 hours |
| /134712 Sept 2026, 01:16 UTC | 786 minutes – 4 days old | 1,230 views ~3 reactions | 60 minutes: 53 → 3.0 hours: 140 → 6.0 hours: 328 → 12 hours: 554 → 24 hours: 743 → 2 days: 943still climbing at last reading | 743measured | 15 hours |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
407 reactions across 126 posts, in 8 distinct kinds. The most used accounts for 58.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 239 | 58.7% | |
| 🔥 | 79 | 19.4% | |
| 👍 | 41 | 10.1% | |
| 🥰 | 17 | 4.18% | |
| 👎 | 10 | 2.46% | |
| 🤔 | 9 | 2.21% | |
| 👏 | 8 | 1.97% | |
| 😁 | 4 | 0.983% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 138 of the 212 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 407 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 212 most recent posts we hold, published 3 August 2026 to 16 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram’s own ‘edited’ marker: 0 of 40 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🗺 Your 48 hours in Tallinn on one map — save it.
👍4❤2🔥2
Photo, posted without a caption
🔥2❤1
🇪🇪 48 hours in Tallinn 🗳 You voted for this one — 15 of 55 votes. Tallinn packs medieval walls, Soviet-era contrasts, and a buzzing modern core into one small, walkable capital. Day 1 • Morning: Climb Toompea Hill to see Toompea Castle, Alexander Nevsky Cathedral and St. Mary's Cathedral, then enjoy the viewpoints. • Afternoon: Wander Old Town past Stenbock House and Estonian Knighthood House, then relax at Maiasmok…
👍4👎1
Where next? The winner gets a full 48-hour plan on Monday ✈️
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
₿ Spend bitcoin in Chiang Mai 🇹🇭 Counted from BTC Map, the community map of places that take bitcoin. 17 places within 10 km of the centre, each confirmed by a visitor in the last 12 months (out of 30 listed). Mostly: restaurants (4), hotels (3), cafés (2), school (1). Among them: Sababa Chiang Mai, Steampunk Studio, Creativitea. Listings are crowd-checked — confirm at the counter before you rely on it.
❤4
🇨🇴 48 hours in Medellín Medellín pairs cable cars over former no-go barrios with salsa clubs and colonial streets, all inside a 22°C mountain valley. Day 1 • Morning: Ride the Metro to Acevedo, take the Metrocable K up to Santo Domingo for valley views, then continue on Line L through forest to Parque Arví. • Afternoon: Head to Comuna 13 for graffiti tours, street art performances, and the covered outdoor escalators…
❤3🔥2🤔1
Photo, posted without a caption
👍2❤1
☀️ Go now: where the weather is right next week Nov 11–Nov 17, from 60 destinations we track. Forecast: Open-Meteo. 🏖 Beach weather 🇦🇪 Dubai — 29°C average high, 1 rainy day 🇺🇸 Miami — 26°C average high, 2 rainy days 🚶 Perfect for walking a city 🇬🇷 Athens — 20°C average high, no rainy days 🇿🇦 Cape Town — 24°C average high, no rainy days ☔ Skip: 🇵🇹 Porto — 178 mm of rain forecast. Forecasts shift — check again bef…
🗺 Your 48 hours in Copenhagen on one map — save it.
🔥7
🇩🇰 48 hours in Copenhagen 🗳 You voted for this one — 20 of 62 votes. Copenhagen packs Viking history, world-class art, and a working harbour you can swim in into one walkable weekend. Day 1 • Morning: Explore Nationalmuseet in Indre By for Bronze Age weapons, Viking runestones, and Danish history exhibits. • Afternoon: Wander Strøget's pedestrian mall past City Hall and Kongens Nytorv, then browse the Latin Quarter'…
🥰3❤1
Photo, posted without a caption
👍5🥰1
Where next? The winner gets a full 48-hour plan on Monday ✈️
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Showing the 12 most recent of 212 posts we hold for @amazingworldtravel. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
The 6 most recent of 87 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Where next? The winner gets a full 48-hour plan on Monday ✈️
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Where next? The winner gets a full 48-hour plan on Monday ✈️
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Where next? The winner gets a full 48-hour plan on Monday ✈️
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Where next? The winner gets a full 48-hour plan on Monday ✈️
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Would you visit Prague for its crypto scene? ✈️₿
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Would you visit Amalfi Coast for its crypto scene? ✈️₿
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 212 most recent posts we hold, published 3 August 2026 to 16 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 60 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 18 November 2026 — this entry's latest reading, not the date you are reading this.
“Amazing World and Travel” (@amazingworldtravel), 935,987 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/amazingworldtravel.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.