Telegram RegisterThe public register of Telegram
Telegram profile photo for мегаящик #1 noli fan

Channel

мегаящик #1 noli fan

@megaashik

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

367subscribers

+10 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003715524828
TypeChannel
Username@megaashik
CreatedBetween 1 February 2026 and 2 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 14 September 2026
On Telegramt.me/megaashik

Topic

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 22 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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

3573673626 August 2026 — 357 subscribers6 August 2026 — 357 subscribers7 August 2026 — 358 subscribers20 August 2026 — 357 subscribers28 August 2026 — 360 subscribers6 September 2026 — 367 subscribers6 August 20266 September 2026
6 measurements spanning 31 days, net +10. 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 356–369 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 16:56367+7
28 Aug 2026, 04:55360+3
20 Aug 2026, 18:36357-1
7 Aug 2026, 03:46358+1
6 Aug 2026, 21:04357no change
6 Aug 2026, 12:19357first reading

Engagement

20 posts held, back to 2 June 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2,656 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 27.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
73027.5%
custom 533682207161374489371326.8%
custom 538676601721091652433112.5%
💘2639.90%
❤‍🔥2037.64%
custom 52739356243221944541776.66%
🔥1736.51%
custom 5447119267021493543230.866%
💔220.828%
custom 5458633833823876696210.791%

Custom emoji. 5 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 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 2,656 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 2 June 2026 to 5 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @megaashik. 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 2 June 2026 to 5 August 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

5 Aug 2026, 18:33 UTC158 views47 reactionsread 6 August 2026

сначала я хотела нарисовать его голым

custom 53368220716137448932212custom 538676601721091652410custom 54586338338238766963

5 Aug 2026, 18:26 UTC432 views81 reactionsread 6 August 2026
Video

Video, posted without a caption

custom 538676601721091652436custom 533682207161374489323❤‍🔥134🔥2💔1💘1custom 54586338338238766961

4 Aug 2026, 21:00 UTC219 views90 reactionsread 6 August 2026
Photo

уроды

custom 538676601721091652447custom 533682207161374489324custom 5458633833823876696172

1 Aug 2026, 19:51 UTC345 views72 reactionsread 6 August 2026
Forwarded from @zhuzhanyPhoto

TW - self-harm!!! Трейд с Шегги

custom 533682207161374489338custom 538676601721091652420❤‍🔥113

31 Jul 2026, 17:21 UTC432 views139 reactionsread 6 August 2026
Photo

Photo, posted without a caption

custom 53867660172109165245943custom 533682207161374489328❤‍🔥9

29 Jul 2026, 18:16 UTC531 views113 reactionsread 6 August 2026
Photo

тв селфхарм

55custom 538676601721091652427💘16custom 53368220716137448939💔6

28 Jul 2026, 21:09 UTC916 views144 reactionsread 6 August 2026
Photo

кто севенолей хотел

custom 533682207161374489359custom 538676601721091652441❤‍🔥3113

28 Jul 2026, 19:31 UTC490 views119 reactionsread 6 August 2026
Photo

Photo, posted without a caption

47❤‍🔥25custom 533682207161374489324custom 538676601721091652412💔8🔥3

26 Jul 2026, 09:53 UTC551 views55 reactionsread 6 August 2026

с днюхой🌟🌟

25custom 533682207161374489315🔥12custom 53867660172109165243

23 Jul 2026, 12:18 UTC748 views135 reactionsread 6 August 2026
Photo

Photo, posted without a caption

62custom 533682207161374489338custom 538676601721091652422💔6💘5❤‍🔥2

22 Jul 2026, 19:34 UTC687 views118 reactionsread 6 August 2026
Photo

ноли

custom 53368220716137448935134custom 538676601721091652427❤‍🔥6

16 Jul 2026, 19:53 UTC≈1,450 views139 reactionsread 6 August 2026
Photo

Photo, posted without a caption

56custom 533682207161374489343custom 538676601721091652427❤‍🔥8💘4🔥1

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

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 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.

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

“мегаящик #1 noli fan” (@megaashik), 367 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/megaashik.

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.