Channel
@gapclosers
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
110subscribers
-2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003877544647 |
|---|---|
| Type | Channel |
| Username | @gapclosers |
| Created | Between 1 February 2026 and 26 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/gapclosers |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 26 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 10:19 | 110 | -1 |
| 30 Aug 2026, 11:53 | 111 | -1 |
| 24 Aug 2026, 05:36 | 112 | +1 |
| 16 Aug 2026, 17:33 | 111 | -1 |
| 9 Aug 2026, 06:47 | 112 | no change |
| 8 Aug 2026, 16:30 | 112 | first reading |
12 posts held, back to 26 July 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
226 reactions across 12 posts, in 20 distinct kinds. The most used accounts for 14.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5319302809819042240 | 32 | 14.2% | |
| custom 5431827877777656846 | 19 | 8.41% | |
| custom 5379586378080209335 | 15 | 6.64% | |
| custom 5316626624286839246 | 14 | 6.19% | |
| custom 5346127101080671559 | 14 | 6.19% | |
| custom 5314578216944421418 | 13 | 5.75% | |
| custom 5364023860435903553 | 13 | 5.75% | |
| custom 5458736586621478499 | 11 | 4.87% | |
| custom 5352903498616827106 | 10 | 4.42% | |
| custom 5460691775993690857 | 10 | 4.42% | |
| custom 5461089391181064293 | 10 | 4.42% | |
| custom 5240243620224715461 | 9 | 3.98% | |
| custom 5240259339805022062 | 9 | 3.98% | |
| custom 5249097884283993610 | 9 | 3.98% | |
| custom 5355207709916416525 | 9 | 3.98% | |
| custom 5240071250302227347 | 8 | 3.54% | |
| custom 5233352018780773035 | 7 | 3.10% | |
| custom 5316630382383225716 | 7 | 3.10% | |
| custom 5276087046455184454 | 4 | 1.77% | |
| custom 5352918041376078873 | 3 | 1.33% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 12 of the 12 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 226 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 26 July 2026 to 7 August 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.
🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸 🧛
custom 52760870464551844544custom 53193028098190422404custom 54610893911810642934custom 52402593398050220622custom 53166303823832257162custom 53145782169444214181custom 54318278777776568461
🚘
custom 53166266242868392467custom 53193028098190422403custom 52490978842839936102custom 53640238604359035532custom 52333520187807730351custom 52400712503022273471custom 52402593398050220621custom 53529180413760788731
Video message, posted without a caption
custom 53795863780802093356custom 53193028098190422405custom 54610893911810642935
Video message, posted without a caption
custom 53640238604359035534custom 54587365866214784994custom 53552077099164165253custom 52333520187807730352custom 53166266242868392462
Video message, posted without a caption
custom 54606917759936908573custom 52400712503022273472custom 52490978842839936102custom 53193028098190422402custom 53529034986168271061custom 53795863780802093351
гуляют мужики
custom 53461271010806715595custom 52490978842839936103custom 52333520187807730352custom 52400712503022273472custom 53166266242868392462
🌟🌟🌟🌟🤩🤩🤩🤩🤩🤩
custom 53193028098190422405custom 53461271010806715595custom 53529034986168271064custom 54318278777776568463custom 52333520187807730351custom 52402436202247154611custom 52402593398050220621custom 53529180413760788731
Photo, posted without a caption
custom 53145782169444214188custom 53193028098190422404custom 53552077099164165254custom 52490978842839936102custom 54587365866214784992custom 52402593398050220621custom 53166266242868392461custom 53166303823832257161
Photo, posted without a caption
custom 53193028098190422406custom 53529034986168271064custom 54606917759936908574custom 53795863780802093352custom 52400712503022273471custom 53166303823832257161custom 53461271010806715591custom 53529180413760788731
🫀
custom 54318278777776568467custom 53145782169444214184custom 53640238604359035533custom 54587365866214784992custom 52333520187807730351custom 53193028098190422401custom 53552077099164165251custom 53795863780802093351
Video message, posted without a caption
custom 52402436202247154617custom 53795863780802093354custom 53166303823832257163custom 53166266242868392462custom 53640238604359035532custom 52402593398050220621custom 53193028098190422401custom 54587365866214784991
🤫
custom 54318278777776568467custom 52402593398050220623custom 53461271010806715593custom 52400712503022273472custom 52402436202247154611custom 53193028098190422401custom 53529034986168271061
Showing the 12 most recent of 12 posts we hold for @gapclosers. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“G.C. – GAP CLOSERS” (@gapclosers), 110 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/gapclosers.
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.