7 Jul 2026, 18:29 UTC349 views11 reactionsread 1 September 2026
Photo
🥸
custom 52264516470136056115custom 52782698261444219423custom 52944353829668949773
Signed ㅤ
Channel
•𝖋𝖔𝖛𝖊𝖗𝖗•
@foverr52
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
202subscribers
+0 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002434004523 |
|---|---|
| Type | Channel |
| Username | @foverr52 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/foverr52 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 16:44 | 202 | no change |
| 1 Sept 2026, 03:31 | 202 | first reading |
Engagement
6 posts held, back to 19 May 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 6 posts for this entry, the most recent from 7 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 15s
- Average length
- 8s
Measured directly from 2 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.
Reaction mix
44 reactions across 6 posts, in 8 distinct kinds. The most used accounts for 18.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5226451647013605611 | 8 | 18.2% | |
| custom 5278269826144421942 | 8 | 18.2% | |
| custom 5294435382966894977 | 8 | 18.2% | |
| custom 5361635609511231872 | 6 | 13.6% | |
| custom 5197605310918839886 | 5 | 11.4% | |
| custom 5226449843127340604 | 4 | 9.09% | |
| custom 5933560313709335590 | 4 | 9.09% | |
| custom 5413341178894493509 | 1 | 2.27% |
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 6 of the 6 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 44 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 19 May 2026 to 7 July 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.
Recent posts
1 Jul 2026, 09:37 UTC246 views8 reactionsread 1 September 2026
Video message
Video message, posted without a caption
custom 52944353829668949774custom 52264498431273406042custom 52264516470136056112
Signed ㅤ
30 Jun 2026, 21:05 UTC197 views4 reactionsread 1 September 2026
сосите мне 18 и я крутой
custom 53616356095112318722custom 51976053109188398861custom 52944353829668949771
Signed ㅤ
30 Jun 2026, 19:21 UTC221 views4 reactionsread 1 September 2026
через полтора часа 18 лет ахуеть кто первый поздравит тот красавчик @foverr52
custom 53616356095112318722custom 52782698261444219421custom 54133411788944935091
Signed ㅤ
1 Jun 2026, 16:59 UTC295 views5 reactionsread 1 September 2026
Forwarded from @chinarider3
ВСЕХ С 274 АВГУСТА!!!!!!
custom 52264498431273406042custom 53616356095112318722custom 52264516470136056111
Signed ㅤ
19 May 2026, 21:57 UTC372 views12 reactionsread 1 September 2026
Photo
суета💯
custom 51976053109188398864custom 52782698261444219424custom 59335603137093355904
Signed ㅤ
Showing the 6 most recent of 6 posts we hold for @foverr52. 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.
Forward network
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.
Mentions
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.
Cite this entry
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“•𝖋𝖔𝖛𝖊𝖗𝖗•” (@foverr52), 202 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/foverr52.
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.