Telegram RegisterThe public register of Telegram

Channel

天河💎叶青青💎天然E乳🐍吻69

@feifeiood

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

336subscribers

-3 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1004343288163
TypeChannel
Username@feifeiood
CreatedBetween 1 June 2026 and 25 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live15 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/feifeiood

Growth

336339337.514 Aug 2026, 15:16 — 339 subscribers15 Aug 2026, 00:57 — 336 subscribers14 Aug 2026, 15:1615 Aug 2026, 00:57
2 measurements taken within a single day, net -3. 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 336–339 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 00:57336-3
14 Aug 2026, 15:16339first reading

Engagement

20 posts held, back to 25 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
113.5%
avg views ÷ 336 subscribers
Avg views / post
381
18 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 1 of 18 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 14 August 2026
Posts held20 (25 July 202614 August 2026)
Views total6,865
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 15:16 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.

What this channel posts

Video runtime
20s
Average length
10s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

14 Aug 2026, 11:21 UTC70 viewsread 14 August 2026
Photo

🎰@niunai881234 叶青青杰尼龟福利抽奖活动 🎁奖品如下: p50优惠券 x 30 pp100优惠券 x 10 🎟参加条件: 加入-天河💎叶青青💎天然E乳🐍吻69 加入-广州杰尼龟修車樂園 加入-广州最全娱乐资源【杰尼龟】 加入-广州杰尼龟【公告】 加入-杰尼龟中转【防丢失】 📝抽奖说明: 1. 兑奖请联系 @niunai881234 2. 优惠券自开奖时间起 7 天内有效。 3. 炸号者中奖作废。 4. 发奖人在发奖前请仔细阅读发奖指引,以防奖品被冒领造成不必要的损失👉 https://t.me/kind216/238 ⏰开奖时间: 2026-08-16 19:20:00

14 Aug 2026, 10:25 UTC76 viewsread 14 August 2026

明天广州开课啦,老公们,喜欢我的大E奶奶嘛😍😍😍

1 Aug 2026, 04:17 UTC462 views0 reactionsread 14 August 2026
Photo

🐻太大也会🈶烦恼哦😄😄😄

30 Jul 2026, 07:53 UTC464 viewsread 14 August 2026

【出击报告】https://t.me/jnggg 【所在位置】天河 【老师艺名】颗糖 【联系方式】@niunai881234 【验证留名】酷酷 【验证时间】7.29 【上课价位】1500pp 【人照几成】人照9分,身材9分 【颜值分数】9 【身材分数】9 【课表服务】课表有的都有,会按摩 【态度分数】10 【优点缺点】🐻真的很大 【推荐程度】10 【体验细节】一进门颗糖的胸真的让人眼前一亮,穿着裙子挺漂亮的,进去会帮你冲洗,然后床上开始口,口的很卖力而且眼神还看着你,运动的过程老师的🐻不停的晃着看着更上火,第一课之后会帮你按摩,这个按摩手法挺好的比其他老师没得说。 温馨提示: 报告仅供参考!

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

Citation-graph rank

Citation-graph rank — 1,405,277 of 1,480,688entries 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.

Mentions

Named by 1 registered channel — 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.

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

“天河💎叶青青💎天然E乳🐍吻69” (@feifeiood), 336 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/feifeiood.

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.