Telegram RegisterThe public register of Telegram
Telegram profile photo for 🍵安妮亞・客評

Channel

🍵安妮亞・客評

@tw720tp

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

12subscribers

+0 since we began measuring on 27 September 2026

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

Register entry

Telegram ID-1003914932633
TypeChannel
Username@tw720tp
CreatedBetween 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live27 September 2026
Measurements held2
On Telegramt.me/tw720tp

Growth

1227 Sept 2026, 02:47 — 12 subscribers27 Sept 2026, 03:22 — 12 subscribers27 Sept 2026, 02:4727 Sept 2026, 03:22
2 measurements taken within a single day. 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 11–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Sept 2026, 03:2212no change
27 Sept 2026, 02:4712first reading

Engagement

7 posts held, back to 10 September 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
2545.2%
avg views ÷ 12 subscribers
Avg views / post
305
7 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
7
of 7 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 23 September 2026
Posts held7 (10 September 2026 – 23 September 2026)
Views total2,138
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 03:22 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

Photos
33

Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

23 Sept 2026, 13:21 UTC843 viewsread 27 September 2026
Photo

#北部輔仁學生 🤩感謝寶寶今日力挺 身高:165大概 年紀:22歲 體重:48 罩杯:E+到F 服務:整體互動自然,配合度不錯,氣氛不會尷尬,實際感受很讚,外型屬於高挑纖細型,身材比例很好,E+~F的條件很有存在感。本人比想像中更有親和力,聊天不會太拘謹,互動起來算輕鬆。 整體來說是身材、外型、互動都有一定水準的類型 是否回約:會,整體體驗滿意 對安妮亞評價:100分,每次找妮妮都能開心,讚 @tw_anya🤩🤩

15 Sept 2026, 06:46 UTC11 viewsread 27 September 2026
Forwarded from @lovely9966Photo

今天不想努力了,先努力把這個鍋戴好🤪

14 Sept 2026, 06:03 UTC80 viewsread 27 September 2026
Photo

昨天凌晨第一次配合的寶寶, 一句「我安排」,就把所有信任都給我了❤️ 第一次合作就這麼阿莎力,真的會讓人很感動啦🤩 有需求一定要主動密安妮亞喲 @TW_anya

12 Sept 2026, 11:53 UTC≈1,140 viewsread 27 September 2026
Photo

一直都在,還是那麼阿莎力🥹 有適合的,有不錯的推薦,寶寶真的二話不說就來了~ 每次都這麼相信我,真的很有默契欸 一路以來的信任,就是給我最好的支持。 謝謝寶寶一直這麼挺我,有適合的我當然也會幫你留意呀💕 聯絡安妮亞: @TW_anya

10 Sept 2026, 18:32 UTC26 viewsread 27 September 2026
Photo

感謝寶寶今日捧場❤️❤️ @TW_anya 姓名:鈴鈴 身高:159 罩杯:D左右 體重:46 年紀:19 有無刺青、抽煙:無 服務: 皮膚白白嫩嫩的,摸起來很滑順,床上反應真實,稍微愛撫就會顫抖,下面顏色粉嫩、濕得也快,舒服時叫聲軟軟的帶著壓抑感,像怕被聽到又忍不住,反而更讓人興奮。從頭到尾配合度都很高,不會趕時間也不會不耐煩,可配合的服務項目也多,整體CP值超高,值得再次回衝。 態度: 溫柔乖巧,學生妹的青澀感,但該配合的部分都很到位,不會扭捏也不會擺架子。會主動互動,也會乖乖聽從引導,整體感受非常舒服。 給妮妮100分評價👍

10 Sept 2026, 18:32 UTC20 viewsread 27 September 2026
Photo

感謝寶今晚3+1💯 讓安妮亞有個完美收官 ‼️職業:北一學生 名字:嘟嘟 157 44 C奶 18歲 🐾評價:健談好聊 很有女友FU 越看越喜歡的類型 @@tw_Anya

10 Sept 2026, 18:31 UTC18 viewsread 27 September 2026
Photo

感謝恩客今日捧場 💃 高挑亮眼 💯曲線吸睛 氣質在線 本人好聊不尷尬,互動自然又有親和力~👍 整體服務讚讚 👍 從見面到相處都很有氣氛, 輕鬆放鬆、🤩不趕不催,時間做足 每一次捧場,都是對安妮亞的信任💯 今天玩得很開心、💯盡興而歸 @TW_anya 信任+1🥰 開心+1🥰 回約+1🥰

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

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

“🍵安妮亞・客評” (@tw720tp), 12 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/tw720tp.

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.