Telegram RegisterThe public register of Telegram
Telegram profile photo for 妞宝NFT礼物(挂售可投稿)

Channel

妞宝NFT礼物(挂售可投稿)

@NFTnnniu

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

1,650subscribers

+114 since we began measuring on 29 August 2026

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

Register entry

Telegram ID-1002503580702
TypeChannel
Username@NFTnnniu
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live17 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/NFTnnniu

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 17 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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,5361,6501,59329 August 2026 — 1,536 subscribers29 August 2026 — 1,536 subscribers1 September 2026 — 1,548 subscribers4 September 2026 — 1,557 subscribers9 September 2026 — 1,585 subscribers13 September 2026 — 1,619 subscribers17 September 2026 — 1,650 subscribers29 August 202617 September 2026
7 measurements spanning 20 days, net +114. 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,519–1,667 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 16:001,650+31
13 Sept 2026, 12:411,619+34
9 Sept 2026, 21:171,585+28
4 Sept 2026, 07:171,557+9
1 Sept 2026, 01:461,548+12
29 Aug 2026, 05:531,536no change
29 Aug 2026, 02:301,536first reading

Engagement

8 posts held, back to 28 August 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.

ERR · 30 days
10.2%
avg views ÷ 1,650 subscribers
Avg views / post
169
8 posts measured
Reaction rate
3.89%
reactions ÷ views · ER floor
Posts in window
8
of 8 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 7 of 8 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 August 2026
Posts held8 (28 August 202628 August 2026)
Views total1,351
Reactions total52
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 02:30 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

52 reactions across 7 posts, in 11 distinct kinds. The most used accounts for 21.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52289584089708906941121.2%
custom 54225845755807260601019.2%
custom 4999387506441979857713.5%
👍611.5%
47.69%
👏47.69%
🔥35.77%
custom 525169546761969563123.85%
custom 529218570486706120023.85%
custom 618171932359419681123.85%
custom 627406094006957480511.92%

Custom emoji. 7 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 7 of the 8 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 52 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 8 most recent posts we hold, published 28 August 2026 to 28 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
4
across the posts below
Posts paid on
1
of 8 we hold a reading for · 13%
Most on one post
4
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @NFTnnniu. 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 8 most recent posts we hold for this entry, published 28 August 2026 to 28 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

28 Aug 2026, 14:50 UTC15 views3 reactionsread 29 August 2026
Photo

🥰🥰🥰🥰

1🔥1custom 52289584089708906941

28 Aug 2026, 14:50 UTC14 views3 reactionsread 29 August 2026
Photo

🥰感谢老板🙂🙂🙂

custom 52289584089708906941custom 52921857048670612001custom 54225845755807260601

28 Aug 2026, 13:14 UTC16 views2 reactionsread 29 August 2026

https://t.me/CNN0999 助推频道🥰 4个助推领 8.8c (名额有限) 找 @nnniu 领取

👍1👏1

28 Aug 2026, 08:50 UTC620 views9 reactionsread 29 August 2026
Photo

代充星星(Telegram Stars)价格: ⭐250星星=5U ⭐500星星 =10U ⭐1000星星=20U ⭐5000星星=100U ➖➖➖➖➖➖➖➖➖➖ ✈️会员代开价格: ⭐3个月高级会员 15U ⭐6个月 高级会员24U ⭐12个月高级会员38U ➖➖➖➖➖➖➖➖➖➖ 🧸联系客服:@nnniu

custom 54225845755807260603custom 52289584089708906942👍1👏1🔥1custom 49993875064419798571

28 Aug 2026, 08:10 UTC216 views10 reactionsread 29 August 2026
Photo

🥰会员🉑代开

👍2👏2custom 49993875064419798572custom 52289584089708906942🔥1custom 62740609400695748051

28 Aug 2026, 07:19 UTC15 views14 reactions4 Starsread 29 August 2026
Photo

🥰可定制

custom 52289584089708906943custom 542258457558072606032custom 49993875064419798572custom 61817193235941968112👍1custom 52921857048670612001

28 Aug 2026, 07:18 UTC440 views11 reactionsread 29 August 2026
Photo

礼物墙🥰

custom 54225845755807260603custom 49993875064419798572custom 52289584089708906942custom 525169546761969563121👍1

Showing the 8 most recent of 8 posts we hold for @NFTnnniu. 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.

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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“妞宝NFT礼物(挂售可投稿)” (@NFTnnniu), 1,650 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/NFTnnniu.

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.