💐💐💐开奖了💐💐💐 中大圈橙橙传媒 @su6357069 福利抽奖 开奖了! 本期总参与人数: 5178 1- 57烈酒花生 获得:大圈优惠券200 2- 花擦 获得:大圈优惠券200 3- 鬼彻 获得:大圈优惠券200 4- 笑衬她颜 获得:中圈优惠100 5- 回到曾经 获得:中圈优惠100 6- 多深情 获得:中圈优惠100 7- 你在大雾里 获得:18.8口令 谨祝中奖用户大吉大利万事顺意
❤1
Channel
@alexdanaigb
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
20,771subscribers
+3,641 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003774723415 |
|---|---|
| Type | Channel |
| Username | @alexdanaigb |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/alexdanaigb |
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @alexdanaigb/695 · this entry3 Aug 2026, 05:38 UTC | @alexxiaoshipin/5623 Aug 2026, 05:38 UTC | 1.00 | under a minute |
| @alexdanaigb/713 · this entry4 Aug 2026, 08:10 UTC | @alexxiaoshipin/5674 Aug 2026, 08:10 UTC | 1.00 | under a minute |
| @alexdanaigb/715 · this entry4 Aug 2026, 08:58 UTC | @alexxiaoshipin/5694 Aug 2026, 08:58 UTC | 1.00 | under a minute |
| @alexdanaigb/736 · this entry7 Aug 2026, 08:08 UTC | @alexxiaoshipin/5757 Aug 2026, 08:08 UTC | 1.00 | under a minute |
| @alexdanaigb/738 · this entry7 Aug 2026, 08:12 UTC | @alexxiaoshipin/5777 Aug 2026, 08:12 UTC | 1.00 | under a minute |
| @alexdanaigb/740 · this entry7 Aug 2026, 08:38 UTC | @alexxiaoshipin/5797 Aug 2026, 08:38 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @alexxiaoshipin | 8 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (7–1) |
| @alexteamreport | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | this entry (4–1) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 2 of the 2 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 13 comparable posts for this entry, running 2 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 3, the earliest publisher we hold is @alexdanaigb — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 14:58 | 20,771 | +271 |
| 16 Sept 2026, 08:17 | 20,500 | +144 |
| 14 Sept 2026, 10:39 | 20,356 | +211 |
| 12 Sept 2026, 16:57 | 20,145 | +175 |
| 10 Sept 2026, 12:55 | 19,970 | +262 |
| 7 Sept 2026, 05:39 | 19,708 | +126 |
| 4 Sept 2026, 11:21 | 19,582 | +135 |
| 2 Sept 2026, 21:19 | 19,447 | +22 |
| 1 Sept 2026, 22:14 | 19,425 | +55 |
| 1 Sept 2026, 00:48 | 19,370 | +101 |
| 31 Aug 2026, 00:04 | 19,269 | +34 |
| 30 Aug 2026, 02:12 | 19,235 | +93 |
| 29 Aug 2026, 00:05 | 19,142 | +107 |
| 27 Aug 2026, 23:15 | 19,035 | +34 |
| 26 Aug 2026, 21:26 | 19,001 | +111 |
| 25 Aug 2026, 21:08 | 18,890 | +192 |
| 24 Aug 2026, 22:58 | 18,698 | +62 |
| 23 Aug 2026, 07:28 | 18,636 | -104 |
| 21 Aug 2026, 19:05 | 18,740 | +8 |
| 20 Aug 2026, 16:58 | 18,732 | first reading |
81 posts held, back to 2 August 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 68 pages of Telegram’s post history, 20 posts per page.
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 17 of 22 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 81 (2 August 2026 – 2 September 2026) |
| Views total | 29,576 |
| Reactions total | 24 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 02:37 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.
Measured directly from 44 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.
72 reactions across 44 posts, in 6 distinct kinds. The most used accounts for 91.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 66 | 91.7% | |
| 💩 | 2 | 2.78% | |
| 👌 | 1 | 1.39% | |
| 👍 | 1 | 1.39% | |
| 👏 | 1 | 1.39% | |
| 😢 | 1 | 1.39% |
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 51 of the 81 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 72 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 81 most recent posts we hold, published 2 August 2026 to 2 September 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.
💐💐💐开奖了💐💐💐 中大圈橙橙传媒 @su6357069 福利抽奖 开奖了! 本期总参与人数: 5178 1- 57烈酒花生 获得:大圈优惠券200 2- 花擦 获得:大圈优惠券200 3- 鬼彻 获得:大圈优惠券200 4- 笑衬她颜 获得:中圈优惠100 5- 回到曾经 获得:中圈优惠100 6- 多深情 获得:中圈优惠100 7- 你在大雾里 获得:18.8口令 谨祝中奖用户大吉大利万事顺意
❤1
【艺名】 #暖暖 【罩杯】#B奶 【位置】 #拱墅 【课费】900p /1700PP 【分类】 #嫩妹 #B奶 #舌吻 #六九 #水中萧 👉报名请点击此处参考示范 工兵500p/1000PP *2,余0(只接受24小时内的工兵报名) 【老师车牌】@nuanlom 【双向联系】 @NuannkBot 【往期报告查看】
❤1
【艺名】 #小奈 【罩杯】#D奶 【位置】 #拱墅 【课费】800p /1500PP 【分类】 #嫩妹 #D奶 #舌吻 #六九 👉报名请点击此处参考示范 工兵500p/900PP *2,余0(只接受24小时内的工兵报名) 【老师车牌】@XIAONAI00612 【双向联系】 【往期报告查看】 报告1
❤4
【艺名】 #可欣 【罩杯】#D奶 【位置】 #拱墅 【课费】1200p / 2300PP 【分类】 #嫩妹 #D奶 #舌吻 #六九 👉报名请点击此处参考示范 工兵700p/1400PP *2,余0(只接受24小时内的工兵报名) 【老师车牌】@kexin689 【双向联系】@Qkxin5bot 【往期报告查看】 报告1
❤3
8️⃣ 月好评报告排行榜 为了方便新加群的狼友选择靠谱的口碑老师,同时激励老师提升客户体验,特举办报告好评排行榜活动 排行榜为老师花名加群内报告数,可点击蓝色字体查看老师榜单的详细内容 1️⃣ 沈薇53 2️⃣ 知允22 3️⃣ 贝贝21 4️⃣ 木瓜瓜20 思思20 5️⃣ 糯糯19 6️⃣ 绘梨衣17 塞壬17 7️⃣ 夏夏14 8️⃣ 米米13 姜樾13 大E学妹13 9️⃣ 玥瑶11 小柔11 1️⃣0️⃣ 蔓越莓10 淼淼10 1️⃣1️⃣ lina9 鑫鑫9 苍井南9 1️⃣2️⃣ 梓琪8 怡怡8 nana8 1️⃣3️⃣ 乐煊7 萧山贝儿7 野结衣7 猫猫7 万涵涵7 1️⃣4️⃣ 允恩6 潼潼6 小肥羊6 娜美6 沐九儿…
❤1
【艺名】 #泡泡 【罩杯】#C奶 【位置】 #西湖 【课费】#800p #1500pp 【分类】 #嫩妹 #舌吻 #六九 👉👉👉工兵报名请点击此处参考示范 工兵500p 900pp*2,余0 (只接受24小时内的工兵报名) 【老师车牌】@xiaopao08 【双向联系】 【往期报告查看】 报告1
❤1
【艺名】 #苏未央 【罩杯】#B奶 【位置】 #拱墅 【课费】#1200p #2100pp 【分类】 #御姐 #兼职 #大长腿 #170cm #舌吻 #六九 👉👉👉工兵报名请点击此处参考示范 工兵800p 1500pp*2,余0 (只接受24小时内的工兵报名) 【老师车牌】 @suweiyang 【双向联系】 @xiexieni88_bot 【往期报告查看】
可乐老师已被盗号,新号 @sxiaoba,各位狼友请注意,不要被骗
😢1
🎰 中大圈橙橙传媒 @su6357069 福利抽奖 📮 抽奖条件: 🎫 加入-杭州💎橙橙茶馆 🎫 加入-杭州💎橙橙茶馆群 🎫 加入-杭州Alex的大奶认证榜单 🎫 加入-杭州Alex教你123 🎫 加入-杭州Alex的小视频 🎫 加入-杭州Alex的大奶新人榜单 🎫 加入-Alex的小视频群2.0 🎁 奖品内容: 大圈优惠券200 × 3 中圈优惠100 × 3 18.8口令 × 1 💡 活动说明: 5天内兑奖,炸号超时名额作废 📅 开奖日期:(UTC+8) 2026年09月03日 06时38分28秒
❤1
【艺名】 #悠悠 【罩杯】#C奶 【位置】 #西湖 【课费】600p 1200pp 【分类】 #嫩妹 #C奶 #水中萧 #舌吻 #六九 #服务 👉👉👉工兵报名请点击此处参考示范 工兵400p 700pp*2,余0 (只接受24小时内的工兵报名) 【老师车牌】 @Ayy_6666 【双向联系】 @Ayyhd_bot 【往期报告查看】 报告1 报告2
❤1
🎰 猫猫奴 @xammn0706 红休回归开课福利抽奖 📮 抽奖条件: 🎫 加入-猫猫奴的小秘密🍼 🎫 加入-杭州Alex的大奶认证榜单 🎫 加入-杭州Alex教你123 🎫 加入-杭州Alex的小视频 🎫 加入-杭州Alex的大奶新人榜单 🎫 加入-Alex的小视频群2.0 🎁 奖品内容: 半价P × 1 200优惠券 × 2 💡 活动说明: 5天内兑奖,炸号超时名额作废 📅 开奖日期:(UTC+8) 2026年08月30日 22时07分58秒
【艺名】#可乐 【罩杯】#D奶 【位置】 #钱塘 【课费】500p / 900PP 【分类】 #嫩妹 #D奶 #BBW #舌吻 #六九 👉报名请点击此处参考示范 工兵300p/500PP *2,余0 (只接受24小时内的工兵报名) 【老师车牌】 @kk20068888 【双向联系】 @kldxw_bot 【往期报告查看】 报告1
❤1
Showing the 12 most recent of 81 posts we hold for @alexdanaigb. 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.
@alexdanaigb edited 8 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
Named by 15 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@alexdanaigb named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“杭州Alex的大奶新人榜单” (@alexdanaigb), 20,771 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/alexdanaigb.
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.