❤️Absolute victory ㅤ
custom 5341395623373459057254

Channel
@oldy_community
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Citations · Cite this entry
122,110subscribers
-1,378 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1002148596064 |
|---|---|
| Type | Channel |
| Username | @oldy_community |
| Description | Oldyest crypto community 🪨 Earn $STONE and feel primal App: @TonOldy_bot |
| Created | Between 1 April 2024 and 31 October 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/oldy_community |
Crypto & trading — 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 9 August 2026 and assigned it the closest of 31 fixed categories, at 71% 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 |
|---|---|---|
| 14 Aug 2026, 15:46 | 122,110 | -210 |
| 13 Aug 2026, 03:53 | 122,320 | -181 |
| 12 Aug 2026, 00:53 | 122,501 | -200 |
| 11 Aug 2026, 04:11 | 122,701 | -169 |
| 10 Aug 2026, 03:51 | 122,870 | -159 |
| 9 Aug 2026, 01:12 | 123,029 | -141 |
| 7 Aug 2026, 22:08 | 123,170 | -163 |
| 7 Aug 2026, 00:36 | 123,333 | -155 |
| 6 Aug 2026, 01:32 | 123,488 | no change |
| 6 Aug 2026, 00:48 | 123,488 | first reading |
20 posts held, back to 11 December 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 21 pagesof 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 20 posts for this entry, the most recent from 22 January 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 August 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.
4,275 reactions across 20 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5341395623373459057 | 4,275 | 100.0% |
Custom emoji. One 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 count beside it isTelegram’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 20 of the 20 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 4,275reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 11 December 2024 to 22 January 2025, 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 @oldy_community. 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 20 most recent posts we hold for this entry, published 11 December 2024 to 22 January 2025. 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.
❤️Absolute victory ㅤ
custom 5341395623373459057254
❤️ Trumpabuga is coming back... ㅤ It won't be long before the chief takes control of the United States of Ugabugia tribe. Press ❤️, if you're waiting for him
custom 5341395623373459057525
❤️ Let's raise a glass of water to those who lived through the Ice Age ㅤ and those who are living through it
custom 5341395623373459057221
❤️ Uga, im tired of eating mammoth salads...ㅤ
custom 5341395623373459057210
❤️ Get out of the cave! Did everyone celebrate the New Year? We've almost eaten the mammoth, so it's time to wake up and move on. ㅤ For example, our chief saw a large supply of $STONE in the quest section ❤️ Complete the quests and get more $STONE!
custom 5341395623373459057157
❤️ Happy New Year 2025 B.C. Uga, it's gotten so cold! Mammoths are especially delicious right now! ㅤ Tribe, we wish you a happy new year! We wish you always a successful hunt and a cave full of stones. ❤️ Happy New Uga-buga!
custom 5341395623373459057211
❤️ Any reputable Uga after an airdrop ㅤ
custom 5341395623373459057271
❤️ End of the Daily Hunt Tribe, we wish to announce the great news: our tribe has achieved a neolithic revolution — we have abandoned hunting in favor of gathering and animal husbandry. Now there will be no more daily hunting! However, you can still earn $STONE by completing tasks and inviting friends. ㅤ ❤️Stay tuned ❤️ Official links: Telegram | Twitter | App
custom 5341395623373459057226
❤️ It's true Word of the day: fork
custom 5341395623373459057140
❤️ OG in place? Word of the day: dumping ㅤ Roll call below: click on ❤️
custom 5341395623373459057278
❤️Which stone is better? Word of the day: simple
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
custom 5341395623373459057251
❤️ The tribe needs you, hunter ㅤ We mean your friends, Uga. We know you have many, so call them all! We'll sit in the cave by the fire, hunt mammoths, eat hamsters ❤️ And in addition to having a good time with your friends, you'll earn $STONE! 1+1+1 = ❤️ Word of the day: book
custom 5341395623373459057138
Showing the 12 most recent of 20 posts we hold for @oldy_community. 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.
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.
❤️Which stone is better? Word of the day: simple
Shares as published, totalling 99%. 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 20 most recent posts we hold, published 11 December 2024 to 22 January 2025. 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.
Citation-graph rank — 927,119 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 3 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Oldy Community” (@oldy_community), 122,110 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/oldy_community.
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.