larp
🌚1

Channel
@work_cum
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Cite this entry
4subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002815776580 |
|---|---|
| Type | Channel |
| Username | @work_cum |
| Created | 3 August 2025 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 2 October 2026 |
| On Telegram | t.me/work_cum |
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 2 October 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 21:15 | 4 | +1 |
| 22 Aug 2026, 17:06 | 3 | +1 |
| 14 Aug 2026, 04:03 | 2 | no change |
| 7 Aug 2026, 18:38 | 2 | first reading |
15 posts held, back to 3 August 2025 — 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 15 posts for this entry, the most recent from 20 July 2026. An engagement rate over an empty window would be a number about nothing.
176 reactions across 14 posts, in 31 distinct kinds. The most used accounts for 9.66% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 17 | 9.66% | |
| custom 5280661667661783545 | 16 | 9.09% | |
| 💘 | 12 | 6.82% | |
| custom 5282833168766904214 | 11 | 6.25% | |
| 🌚 | 11 | 6.25% | |
| custom 5280952694645758500 | 9 | 5.11% | |
| custom 5280981256178278136 | 9 | 5.11% | |
| ❤🔥 | 8 | 4.55% | |
| custom 5346008847746108438 | 7 | 3.98% | |
| 😍 | 7 | 3.98% | |
| 🍌 | 6 | 3.41% | |
| custom 5244469773554698739 | 5 | 2.84% | |
| custom 5248994714874560514 | 5 | 2.84% | |
| custom 5249297467119253555 | 5 | 2.84% | |
| 🍓 | 5 | 2.84% | |
| custom 5282769891013728684 | 4 | 2.27% | |
| custom 5282980292871626064 | 4 | 2.27% | |
| 😘 | 4 | 2.27% | |
| 🥰 | 4 | 2.27% | |
| custom 5244780574568107932 | 3 | 1.70% | |
| 11 further kinds | 24 | 13.6% |
Custom emoji. 11 of the rows above are 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 14 of the 15 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 176 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 3 August 2025 to 20 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @work_cum. 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 15 most recent posts we hold for this entry, published 3 August 2025 to 20 July 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.
larp
🌚1
Video, posted without a caption
🌚1
Video, posted without a caption
🌚1
Video, posted without a caption
🌚1
Video, posted without a caption
🌚1
Video, posted without a caption
🌚1
Video, posted without a caption
custom 52108227077000681461custom 52444697735546987391custom 52447805745681079321custom 52827698910137286841custom 53439394637834125321custom 53844127616797541671
Video, posted without a caption
custom 52827698910137286842custom 52108227077000681461custom 52444697735546987391custom 52447805745681079321custom 53439394637834125321custom 53842612481184541411custom 53844127616797541671
Video, posted without a caption
custom 52806616676617835453custom 52444697735546987391custom 52447805745681079321custom 52489947148745605141custom 52492974671192535551custom 52827698910137286841custom 53755221020676232341custom 53842612481184541411
Video, posted without a caption
custom 52806616676617835456custom 52809812561782781365custom 53460088477461084385custom 52828331687669042144❤🔥2🌚2custom 52422020608871861922custom 52444697735546987392
Video, posted without a caption
custom 52809812561782781364🌚3custom 52806616676617835453custom 52809526946457585003custom 52829802928716260642❤1❤🔥1💘1
Video, posted without a caption
❤6custom 52806616676617835454💘3custom 52492974671192535552custom 52829802928716260642custom 53460088477461084382❤🔥1🍌1
Showing the 12 most recent of 15 posts we hold for @work_cum. 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“484æ” (@work_cum), 4 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/work_cum.
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.