Telegram RegisterThe public register of Telegram
Telegram profile photo for althoax

Channel

althoax

@althoax

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,258subscribers

+165 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002619786382
TypeChannel
Username@althoax
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live16 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/althoax

Topic

Giveaways & airdrops — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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.

Growth

1,0841,3011,192.59 August 2026 — 1,093 subscribers9 August 2026 — 1,093 subscribers9 August 2026 — 1,092 subscribers12 August 2026 — 1,084 subscribers15 August 2026 — 1,156 subscribers18 August 2026 — 1,169 subscribers21 August 2026 — 1,269 subscribers24 August 2026 — 1,240 subscribers28 August 2026 — 1,228 subscribers31 August 2026 — 1,223 subscribers3 September 2026 — 1,221 subscribers8 September 2026 — 1,301 subscribers13 September 2026 — 1,274 subscribers16 September 2026 — 1,258 subscribers1,2589 August 202616 September 2026
14 measurements spanning 39 days, net +165. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,051–1,334 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 20:401,258-16
13 Sept 2026, 01:591,274-27
8 Sept 2026, 19:571,301+80
3 Sept 2026, 02:391,221-2
31 Aug 2026, 08:051,223-5
28 Aug 2026, 01:181,228-12
24 Aug 2026, 21:591,240-29
21 Aug 2026, 00:541,269+100
18 Aug 2026, 09:471,169+13
15 Aug 2026, 13:381,156+72
12 Aug 2026, 04:171,084-8
9 Aug 2026, 14:171,092-1
9 Aug 2026, 01:001,093no change
9 Aug 2026, 00:471,093first reading

Engagement

20 posts held, back to 18 July 2026the 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 20 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

247 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 38.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54201790846573241289438.1%
custom 53530899818018536942911.7%
custom 52873366309552923712811.3%
custom 5235543435649232997249.72%
custom 5379713234234279841249.72%
custom 5442616341703969974166.48%
custom 5192893766154868939114.45%
custom 535495195320388338493.64%
custom 536616397392002294272.83%
custom 535510929503580761831.21%
custom 537074267105057207420.81%

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 9 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 247 reactions 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 18 July 2026 to 1 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.

Recent posts

1 Aug 2026, 20:30 UTC199 views4 reactionsread 9 August 2026

🎉 Розыгрыш завершен! 🏆 Победители: 1. @ymbvdele 🔍 Проверить результаты

custom 53707426710505720742custom 53797132342342798412

Signed Random Beast 🏆

31 Jul 2026, 20:30 UTC470 views3 reactionsread 9 August 2026

🎉 Розыгрыш завершен! 🏆 Победители: 1. @Fanghop000 🔍 Проверить результаты

custom 53797132342342798413

Signed Random Beast 🏆

31 Jul 2026, 07:52 UTC317 views8 reactionsread 9 August 2026

Сегодня итоги, участвуйте. (Накруток нет)

custom 54426163417039699748

Signed alt

27 Jul 2026, 20:30 UTC454 viewsread 9 August 2026

🎉 Розыгрыш завершен! 🏆 Победители: 1. @allternattiva 🔍 Проверить результаты

Signed Random Beast 🏆

26 Jul 2026, 18:09 UTC414 viewsread 9 August 2026

Завтра итоги ещё на одно нфт, не отписываемся

Signed alt

26 Jul 2026, 18:00 UTC439 viewsread 9 August 2026

🎉 Розыгрыш завершен! 🏆 Победители: 1. @allternattiva 2. @azasney 3. @KRsail 4. @chifirava 5. @sigmavhui 6. @rolictor 7. @eowixwa 8. @Crazy_Regina_Boom_Devochka66 9. @krisxvk 10. @Salt_BUT 🔍 Проверить результаты

Signed Random Beast 🏆

26 Jul 2026, 10:36 UTC429 viewsread 9 August 2026
Photo

Проверяйте, выполнены ли все условия или нет. Итоги уже сегодня вечером

Signed alt

25 Jul 2026, 20:46 UTC660 views57 reactionsread 9 August 2026
Photo

Розыгрыш Pepe арендой на 2 дня Условия для участия в конкурсе: Подписаться на 2 канала @althoax @xelwik Поставить реакцию на пост Нажать кнопку участвовать Итоги 01.08 в 23:30 по МСК

custom 542017908465732412827custom 535308998180185369411custom 53549519532038833849custom 53661639739200229424custom 53551092950358076183custom 53797132342342798413

Signed Random Beast 🏆

25 Jul 2026, 14:56 UTC455 viewsread 9 August 2026

Добейте 100 участников, итоги уже завтра

Signed alt

25 Jul 2026, 14:27 UTC898 views12 reactionsread 9 August 2026
Photo

Розыгрыш на NFT подарок Условия для участия в конкурсе: Подписаться на 2 канала @althoax @balencaman По желанию пригласить друзей по реф. ссылке для увеличения шансов При победе твинка или бота будет рерол Итоги 31.07 в 23:30 по МСК

custom 523554343564923299712

Signed Random Beast 🏆

Showing the 12 most recent of 20 posts we hold for @althoax. 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

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.

Mentions

Named by 4 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.

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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“althoax” (@althoax), 1,258 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/althoax.

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.