BNB DAO Close upd: https://t.me/groxliveofficial/20
😁79❤32🔥13⚡5💯2🫡2👍1🤩1

Channel
@tonstationgames
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Posts edited after publishing · Polls · Citations · Handles named that no longer answer · Telegram's recommendations · Domains linked from posts · Cite this entry
2,895,535subscribers
-557,850 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1002204393727 |
|---|---|
| Type | Channel |
| Username | @tonstationgames |
| Description | Premium Game Distribution TG Platform by Sidus Heroes & SuperVerse. Exclusive airdrops, Premium game content, Epic community & more. $MRSOON token at the heart – your gateway to Web3 of tomorrow. Join!📍Official links: https://linktr.ee/tonstation |
| Created | 21 June 2024 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/tonstationgames |
Gaming — 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 99% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @sidus_heroes_channel | 10 (8/8 hand-verifiable sample passed) | 0.99 | 3 minutes | this entry (6–4) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 740 comparable posts for this entry, running 25 June 2024 to 4 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @tonstationgames — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 6 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 22:16 | 2,895,535 | -4,716 |
| 5 Nov 2026, 22:46 | 2,900,251 | -4,573 |
| 5 Nov 2026, 00:55 | 2,904,824 | -14,833 |
| 3 Nov 2026, 22:40 | 2,919,657 | -15,858 |
| 3 Nov 2026, 00:51 | 2,935,515 | -4,752 |
| 2 Nov 2026, 00:04 | 2,940,267 | -6,336 |
| 31 Oct 2026, 22:38 | 2,946,603 | -6,635 |
| 30 Oct 2026, 20:35 | 2,953,238 | -6,833 |
| 29 Oct 2026, 19:19 | 2,960,071 | -5,664 |
| 28 Oct 2026, 20:10 | 2,965,735 | -5,760 |
| 27 Oct 2026, 22:06 | 2,971,495 | -6,193 |
| 26 Oct 2026, 19:37 | 2,977,688 | -4,310 |
| 25 Oct 2026, 22:31 | 2,981,998 | -3,893 |
| 24 Oct 2026, 20:11 | 2,985,891 | -5,389 |
| 23 Oct 2026, 23:36 | 2,991,280 | -4,742 |
| 23 Oct 2026, 02:57 | 2,996,022 | -6,679 |
| 22 Oct 2026, 03:46 | 3,002,701 | -8,078 |
| 20 Oct 2026, 19:49 | 3,010,779 | -6,354 |
| 19 Oct 2026, 21:28 | 3,017,133 | -6,034 |
| 18 Oct 2026, 21:11 | 3,023,167 | first reading |
783 posts held, back to 21 June 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 4,225 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.
| Window | Rolling 30 days · latest post in window 20 October 2026 |
|---|---|
| Posts held | 783 (21 June 2024 – 20 October 2026) |
| Views total | 253,800 |
| Reactions total | 2,400 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 04:30 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 7 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 10 of this channel’s own posts over the last 30 days: across 10 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 21 hours of being posted; a typical post has already reached 28.9% of its 24-hour view count within the first hour, and 64.3% within the first six; the median 24-hour reach across those posts is 9,950 views — 0.344% of this channel’s own subscriber count (90th percentile 11,550).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /85520 Oct 2026, 11:02 UTC | 12257 minutes – 7 days old | 16,000 views ~81 reactions | 60 minutes: 2,440 → 3.0 hours: 4,180 → 6.0 hours: 5,470 → 12 hours: 6,880 → 24 hours: 8,250 → 2 days: 10,000 → 7 days: 16,000still climbing at last reading | 8,250measured | 22 hours |
| /85419 Oct 2026, 15:47 UTC | 12213 minutes – 7 days old | 18,200 views ~315 reactions | 60 minutes: 2,620 → 3.0 hours: 4,390 → 6.0 hours: 5,520 → 12 hours: 6,730 → 24 hours: 10,300 → 2 days: 12,300 → 7 days: 18,200still climbing at last reading | 10,300measured | 20 hours |
| /85319 Oct 2026, 10:51 UTC | 9534 minutes – 7 days old | 15,700 views ~244 reactions | 60 minutes: 2,524 interp. → 3.0 hours: 4,420 → 6.0 hours: 6,390 → 12 hours: 8,100 → 24 hours: 9,600 → 2 days: 11,500 → 7 days: 15,700still climbing at last reading | 9,600measured | 10 hours |
| /85218 Oct 2026, 10:23 UTC | 8913 minutes – 7 days old | 15,300 views ~160 reactions | 60 minutes: 2,410 → 3.0 hours: 4,120 → 6.0 hours: 5,560 → 12 hours: 7,130 → 24 hours: 8,650 → 2 days: 12,300 → 7 days: 15,300still climbing at last reading | 8,650measured | 17 hours |
| /85116 Oct 2026, 09:33 UTC | 11336 minutes – 7 days old | 19,400 views ~164 reactions | 60 minutes: 2,528 interp. → 3.0 hours: 4,190 → 6.0 hours: 5,570 → 12 hours: 7,170 → 24 hours: 8,420 → 2 days: 10,300 → 7 days: 19,400still climbing at last reading | 8,420measured | 37 hours |
| /85015 Oct 2026, 09:09 UTC | 1098 minutes – 7 days old | 21,100 views ~391 reactions | 60 minutes: 3,256 interp. → 3.0 hours: 5,460 → 6.0 hours: 7,250 → 12 hours: 9,450 → 24 hours: 11,400 → 2 days: 13,700 → 7 days: 21,100still climbing at last reading | 11,400measured | 19 hours |
| /84915 Oct 2026, 09:09 UTC | 1099 minutes – 7 days old | 21,400 views ~97 reactions | 60 minutes: 3,299 interp. → 3.0 hours: 5,500 → 6.0 hours: 7,260 → 12 hours: 9,430 → 24 hours: 11,300 → 2 days: 13,700 → 7 days: 21,400still climbing at last reading | 11,300measured | 21 hours |
| /84814 Oct 2026, 08:34 UTC | 12227 minutes – 7 days old | 21,000 views ~326 reactions | 60 minutes: 3,190 → 3.0 hours: 5,240 → 6.0 hours: 6,940 → 12 hours: 9,010 → 24 hours: 10,900 → 2 days: 14,600 → 7 days: 21,000still climbing at last reading | 10,900measured | 22 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.
10,990 reactions across 31 posts, in 29 distinct kinds. The most used accounts for 35.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3,846 | 35.0% | |
| 😁 | 2,311 | 21.0% | |
| 👍 | 1,718 | 15.6% | |
| 🔥 | 707 | 6.43% | |
| 🤪 | 417 | 3.79% | |
| 🤔 | 334 | 3.04% | |
| 🙈 | 307 | 2.79% | |
| 👏 | 291 | 2.65% | |
| 😱 | 171 | 1.56% | |
| 😈 | 148 | 1.35% | |
| 🥰 | 104 | 0.946% | |
| 🐳 | 80 | 0.728% | |
| 👾 | 79 | 0.719% | |
| ⚡ | 75 | 0.682% | |
| 🙏 | 65 | 0.591% | |
| 🆒 | 64 | 0.582% | |
| 🤝 | 57 | 0.519% | |
| 🏆 | 46 | 0.419% | |
| 💋 | 46 | 0.419% | |
| 🦄 | 27 | 0.246% | |
| 9 further kinds | 97 | 0.883% |
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 781 of the 783 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 6,662,313 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 783 most recent posts we hold, published 21 June 2024 to 20 October 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @tonstationgames. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 783 most recent posts we hold for this entry, published 21 June 2024 to 20 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 1 of 10 posts held from the last 30 days (10.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).
BNB DAO Close upd: https://t.me/groxliveofficial/20
😁79❤32🔥13⚡5💯2🫡2👍1🤩1
Alright, you jokers. The pool is open — where is everyone? You were unstoppable in the vote. We counted the responses, were surprised by the scale, and shared the results with our partners. Now the pool is open on XDAO, but there’s barely any activity. XDAO is waiting for you. It’s a tool that lets us try something together: fund a pool, launch the strategy, and follow the results. If you planned to participate, n…
😁121❤100👍67🙈15🤔10😱9🤪7🔥5
Our First Public A2 Pool: Contributions Are Open From voting to launch. The pool operates on BNB Chain. Contributions are accepted in USDT, and participants receive A2POOL tokens. What happens next? Once the pool is filled, contributions will close. The funds will undergo AML screening. After the checks are successfully completed, trading will begin using our G1 strategy, offered by our partners under the name A2…
👍119❤71😁37👏10🤪7🤔6😱4🐳3
Our partners will publish the smart contract address and participation terms. Contributions will close once the pool is filled. The funds will then undergo AML screening, and trading with the A2 strategy will begin after the checks are successfully completed. We’ll be able to follow the process together: our partners are preparing a public dashboard showing trading activity and results in real time. Based on your v…
😁72👍47❤42🤪8
You surprised us Voting has closed. Against a falling market, you supported testing the algorithm and creating a community pool. Here’s the estimated total based on the selected amounts: — 707 votes × $25 = $17,675 — 234 votes × $100 = $23,400 — 366 votes × $500 = $183,000 Total: $224,075. Almost a quarter of a million dollars. That’s a serious response for a first experiment. We understand that some people vote…
❤84😁38👏19🎉8🔥7🤪6👾4🥰4
How much?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
❤157👍132😁50🤪27🐳9👏9🤔9⚡6
TON STATION: the pool is happening! Hi everyone! In the previous vote, you supported launching a community pool with our partners at grox.live. Now we’re taking the next step: estimating how much we’re ready to contribute together. This poll will help us set a realistic target for the pool. Please take it seriously. How much do you personally plan to contribute? — More than 25 — More than 100 — More than 500 Cho…
❤54😁23👏11🔥9⚡2💋1
Posted without readable text
❤173🤪58👍39😁21😱14👏10⚡7🐳7
Posted without readable text
👍185❤88😁47🙈26🐳11
You helped shape the next step When we introduced grox.live, we were curious to see how the community would respond to their trading strategy. The response was clear: after the post, our partners received many inquiries — from managing individual accounts to creating shared DAO pools. The grox.live team told us they hadn’t expected this level of interest. We’re glad to see people in TON STATION exploring new tools …
❤74😁30👏17👍5🤪3
grox.live and CoinRate: launching A2 We have agreed to partner with CoinRate and are launching our G1 trading strategy on their platform, where it will be offered under the name A2. grox.live develops trading algorithms and capital management solutions. CoinRate specializes in crypto asset management, market making, and liquidity. We are now joining forces to launch A2. A2 is built on G1, a systematic, multi-facto…
👍83❤57🤪19😁15🔥7🙈6
TON Station Update Hello, GramStation 😂 (ha-ha-ha) We’ve integrated the payment system and launched the Boss Event. We’re currently testing the boss mechanics. This is a temporary activity to give everyone something to do while we continue preparing the new season. Gram Points and special quests where you’ll be able to farm them separately will be introduced soon. We also want to note that we see all the messages…
❤451👏147😁84👍42🤔37🥰35⚡31🔥24
Showing the 12 most recent of 783 posts we hold for @tonstationgames. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@tonstationgames edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
How much?
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 783 most recent posts we hold, published 21 June 2024 to 20 October 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 26 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
@tonstationgames named 11 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 7 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 1,364 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.
32 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“TON Station” (@tonstationgames), 2,895,535 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/tonstationgames.
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.