剛滿18歲的莊敬學生妹 有人幫忙救場嗎 潼潼給救場價格 急急急

Channel
潼潼の 北部名單 🇹🇼
@ons279
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
7,810subscribers
-235 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001949220933 |
|---|---|
| Type | Channel |
| Username | @ons279 |
| Description | 北部:台北 新北 桃園龜山 所有頻道鏈接入口 資訊更新都會在這邊公佈 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/ons279 |
Topic
Adult — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 23:10 | 7,810 | -13 |
| 1 Nov 2026, 12:24 | 7,823 | -7 |
| 29 Oct 2026, 19:28 | 7,830 | -8 |
| 26 Oct 2026, 08:36 | 7,838 | -16 |
| 23 Oct 2026, 01:46 | 7,854 | -10 |
| 20 Oct 2026, 10:55 | 7,864 | -5 |
| 17 Oct 2026, 05:10 | 7,869 | -4 |
| 14 Oct 2026, 12:49 | 7,873 | -7 |
| 11 Oct 2026, 11:37 | 7,880 | -2 |
| 4 Oct 2026, 20:20 | 7,882 | -6 |
| 25 Sept 2026, 14:21 | 7,888 | -32 |
| 14 Sept 2026, 23:01 | 7,920 | -9 |
| 11 Sept 2026, 13:57 | 7,929 | -24 |
| 7 Sept 2026, 04:00 | 7,953 | -16 |
| 2 Sept 2026, 10:29 | 7,969 | +2 |
| 30 Aug 2026, 04:26 | 7,967 | -13 |
| 26 Aug 2026, 20:56 | 7,980 | -5 |
| 23 Aug 2026, 14:37 | 7,985 | -9 |
| 19 Aug 2026, 23:05 | 7,994 | -19 |
| 16 Aug 2026, 21:13 | 8,013 | first reading |
Engagement
39 posts held, back to 30 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 24 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 8.65%
- avg views ÷ 7,810 subscribers
- Avg views / post
- 675
- 7 posts measured
- Reaction rate
- 0.103%
- reactions ÷ views · ER floor
- Posts in window
- 7
- of 39 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 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 October 2026 |
|---|---|
| Posts held | 39 (30 July 2026 – 29 October 2026) |
| Views total | 4,727 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 11:50 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
- ≈1,750
- Videos
- ≈6
- Links
- ≈832
Lifetime counters from Telegram’s own channel header, read 5 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
3 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 100.0% |
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 4 of the 39 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 39 most recent posts we hold, published 30 July 2026 to 29 October 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 7 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
【晚間特價】 周瑜 167 50 D 25歲 特價:6000 地區:雙北 🌐 潼潼の賴 ons9 ⭐ Gleezy搜 ons966 🌐 私密潼潼 @ons966
【晚間特價】 雪瑤 165 50 D 28歲 特價:5000 地區:新竹 🌐 潼潼の賴 ons9 ⭐ Gleezy搜 ons966 🌐 私密潼潼 @ons966
#北部可約 #學生妹 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 👩🦳 💖悠悠 161/45/C/19歲 世新大學 💖小貝 156/42/B/20歲 大同大學 💖雅文 166/48/C/22歲 輔仁大學 💖果果 155/51/E/22歲 真理大學 💖豆芽 161/44/C/21歲 淡江大學 花名冊 https://t.me/+UUFOEF9JF7gxNDFl 🌐 潼潼の賴 ons9 🌐 私密潼潼 @ons966 ⭐ Gleezy 搜 ons966
北部的哥哥密我一下 有驚喜 🌐 @ons966
潼潼的私藏貨 今天公佈出來了 有很多VIP還沒加入VIP群的 本來只打算推VIP 但國慶當做福利送出來給大家約 這個妹超推薦的高級尤物 現在是驚喜優惠價格 這位臉蛋漂亮 又超有氣質 潼潼真的很推薦
❤1
最近潼潼在主推的大一學生妹 可可最新客評 🧼終於試車完了 客評: 這個外貌可以! 蠻好聊的 還不錯啊 都有到我的標準 服務哦 也還不錯 基本的都有 然後吹功我覺得蠻厲害的 ➖➖➖➖➖➖➖➖➖ 🤍點擊這裡一鍵加入所有頻道 花名冊 https://t.me/+UUFOEF9JF7gxNDFl 🌐 潼潼の賴 ons9 ⭐ Gleezy搜 ons966 🌐 私密潼潼 @ons966
前天剛面試的大一新妹 今天下課晚上來第一次來兼職的 臉蛋甜甜的 很乖 小隻有料 160.45.D.19歲 第一個客人有折扣 🌐 潼潼の賴 ons9 🌐 私密潼潼 @ons966
🗺 #新竹推薦 新妹 🩷 笙笙 161.48.D.21歲 性格活潑 性慾強 很喜歡自慰 新妹服務可以探索 開發 調教 🤍點擊這裡一鍵加入所有頻道 🌐 LINE:ons9 🌐 密Tg: @ons966 ⭐ Gleezy 搜 ons966
🗺 #雙北推薦 新妹 🩷小葵 159.44.C.20歲 超甜 鄰家妹妹 很乖 聲音很甜 新妹服務可以探索 開發 調教 🤍點擊這裡一鍵加入所有頻道 🌐 LINE:ons9 🌐 密Tg: @ons966 ⭐ Gleezy 搜 ons966
回報一下啦啦隊的評價👍 目測年齡:25 目測身高:159 目測體重:47 脫衣目測罩杯:C 約會過程分享:很會聊天,一上來就抱住我,然後帶我去沖澡,在浴室就一直很渴望的樣子,很騷,到床上後,我叫她自慰給我看,她就一直自慰,然一邊自慰還一邊淫叫,最後自己自慰到高潮還有噴水。 是否值得推薦:是 是否想要回約:會 對潼潼的安排評價:很厲害,臨時都能安排到 ➖➖➖➖➖➖➖➖➖ 🤍點擊這裡一鍵加入所有頻道 花名冊 https://t.me/+YRLkgOnRmqI4NjBl 預約點這裡:👇🏻 ⭐ Gleezy搜 ons966 🌐 LINE:ons9 🌐 @ons966
買一送五 買一送五 買一送五 有興趣密我 🌐 潼潼の賴 ons9 🌐 私密潼潼 @ons966
Showing the 12 most recent of 39 posts we hold for @ons279. 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.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“潼潼の 北部名單 🇹🇼” (@ons279), 7,810 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/ons279.
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.