Telegram RegisterThe public register of Telegram
Telegram profile photo for مسابقات وجوائز

Channel

مسابقات وجوائز

@ll32n

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Posts edited after publishing · Cite this entry

11,323subscribers

+1,124 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003849804662
TypeChannel
Username@ll32n
CreatedBetween 1 February 2026 and 21 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live29 October 2026
Measurements held42
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/ll32n

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 the other topics.

Growth

9,48512,14110,8136 August 2026 — 10,199 subscribers6 August 2026 — 10,153 subscribers7 August 2026 — 10,121 subscribers8 August 2026 — 10,027 subscribers9 August 2026 — 10,001 subscribers10 August 2026 — 9,935 subscribers13 August 2026 — 9,907 subscribers17 August 2026 — 9,616 subscribers20 August 2026 — 9,529 subscribers24 August 2026 — 9,542 subscribers27 August 2026 — 9,485 subscribers30 August 2026 — 11,060 subscribers31 August 2026 — 11,187 subscribers1 September 2026 — 11,352 subscribers2 September 2026 — 11,339 subscribers4 September 2026 — 11,890 subscribers6 September 2026 — 12,141 subscribers9 September 2026 — 12,056 subscribers12 September 2026 — 11,980 subscribers13 September 2026 — 11,927 subscribers15 September 2026 — 11,947 subscribers17 September 2026 — 11,920 subscribers26 September 2026 — 11,417 subscribers4 October 2026 — 11,359 subscribers9 October 2026 — 11,286 subscribers13 October 2026 — 11,238 subscribers14 October 2026 — 11,237 subscribers15 October 2026 — 11,227 subscribers16 October 2026 — 11,258 subscribers17 October 2026 — 11,266 subscribers18 October 2026 — 11,327 subscribers19 October 2026 — 11,356 subscribers20 October 2026 — 11,440 subscribers21 October 2026 — 11,466 subscribers22 October 2026 — 11,389 subscribers23 October 2026 — 11,272 subscribers24 October 2026 — 11,225 subscribers25 October 2026 — 11,263 subscribers26 October 2026 — 11,279 subscribers27 October 2026 — 11,302 subscribers28 October 2026 — 11,308 subscribers29 October 2026 — 11,323 subscribers11,3236 August 202629 October 2026
42 measurements spanning 85 days, net +1,124. 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 9,087–12,539 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 42
Measured (UTC)SubscribersChange
29 Oct 2026, 17:2011,323+15
28 Oct 2026, 13:5611,308+6
27 Oct 2026, 11:4511,302+23
26 Oct 2026, 13:2911,279+16
25 Oct 2026, 15:5911,263+38
24 Oct 2026, 18:0811,225-47
23 Oct 2026, 20:1711,272-117
22 Oct 2026, 22:3111,389-77
21 Oct 2026, 16:5511,466+26
20 Oct 2026, 15:0711,440+84
19 Oct 2026, 18:1111,356+29
18 Oct 2026, 18:3611,327+61
17 Oct 2026, 18:3111,266+8
16 Oct 2026, 15:2911,258+31
15 Oct 2026, 14:3911,227-10
14 Oct 2026, 14:1611,237-1
13 Oct 2026, 06:5111,238-48
9 Oct 2026, 02:1811,286-73
4 Oct 2026, 16:5611,359-58
26 Sept 2026, 14:1811,417first reading

Engagement

273 posts held, back to 21 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 40 pages 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 273 posts for this entry, the most recent from 2 September 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

852 reactions across 205 posts, in 2 distinct kinds. The most used accounts for 99.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍓85099.8%
custom 522214836895587790020.235%

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 is 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 215 of the 273 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 854 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 273 most recent posts we hold, published 21 July 2026 to 2 September 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.

Telegram Stars

Stars received
2,702
across the posts below
Posts paid on
57
of 268 we hold a reading for · 21%
Most on one post
393
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ll32n. 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 273 most recent posts we hold for this entry, published 21 July 2026 to 2 September 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.

Recent posts

2 Sept 2026, 20:24 UTC306 views1 reactionsread 3 September 2026

للمشاركه دز اسمك هنا( @y_9_m )⭐ للمحضورين دز اسمك ( @ll32ibot ) ⭐

🍓1

2 Sept 2026, 18:55 UTC362 views1 reactions300 Starsread 3 September 2026

نور دخلت تاخذها غصب

🍓1

2 Sept 2026, 11:51 UTC354 views1 reactionsread 3 September 2026

مسابقه على( هاي الحلوه ) 😗 القوانين الرشق + وهمي + مغادره = خصم2 ❌ تبدأ4:00وتنتهي غداً نفس الوقت الوقت✅ قابله للتمديد 🥇 كل نجمه صوتين ⭐️ استقبل رصيد 5 اسيا =250نجمه💵 ملاحضه ماكو شد الغي المسابقه 🤝 ملاحضه: استقبل مقتنيات احسبهة ×٣🐶 قناة المسابقه ( @ll32n ) 📰 للتسجيل ( @y_9_m ) ✅

🍓1

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

Posts edited after publishing

@ll32n edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
3 September 2026
Most recent edit
3 September 2026

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

“مسابقات وجوائز” (@ll32n), 11,323 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/ll32n.

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.