Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州Alex总是123

Channel

杭州Alex总是123

@whyalexalways1234

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

30,371subscribers

+6,647 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003477944298
TypeChannel
Username@whyalexalways1234
Description【大奶群聊】 @alexteach123 【大奶榜单】 @alexteamreport 【工兵频道】 @alexdanaigb 【小视频区】 @alexxiaoshipin 【报告频道】 @alexreportchannel #频道主个人审美: 匈奴人(C-E杯最佳,挺拔饱满不下垂,不外扩,乳晕乳头正常大小,优先细支硕果) #审美排序: 身材>情绪>颜值>服务 (舌吻和69为必选项) #业务范围: TG账号, 代开会员, 典藏礼物, 永久用户名, 实名认证, VPN节点, 换绑手机号等
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/whyalexalways1234

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 47% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 4 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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.

Matching posts — open both and compare (4 of the pairs behind the counts below)
Posted firstThenOverlapGap
@alexxiaoshipin/5581 Aug 2026, 08:30 UTC@whyalexalways1234/396 · this entry1 Aug 2026, 08:30 UTC1.00under a minute
@alexxiaoshipin/68531 Aug 2026, 19:11 UTC@whyalexalways1234/436 · this entry31 Aug 2026, 19:11 UTC1.00under a minute
@alexxiaoshipin/6913 Sept 2026, 04:38 UTC@whyalexalways1234/438 · this entry3 Sept 2026, 04:38 UTC1.00under a minute
@alexxiaoshipin/10313 Nov 2026, 18:52 UTC@whyalexalways1234/507 · this entry3 Nov 2026, 18:52 UTC0.95under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@alexxiaoshipin5 (5/5 hand-verifiable sample passed)0.99under a minutethis entry (5–0)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 29 comparable posts for this entry, running 19 July 2026 to 14 November 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 4 channels, the one whose matching posts we hold earliest is @alexxiaoshipin. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 16 November 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.

Channels linked by matching posts

This channel is in a group of 4 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.

Growth

23,72430,37127,047.56 August 202614 November 2026
66 measurements spanning 100 days, net +6,647. 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 22,727–31,368 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
14 Nov 2026, 20:2930,371+194
11 Nov 2026, 21:3530,177+120
10 Nov 2026, 03:0730,057+69
8 Nov 2026, 14:0529,988+24
7 Nov 2026, 07:0229,964+58
6 Nov 2026, 04:5829,906+74
5 Nov 2026, 02:0029,832+82
4 Nov 2026, 03:2829,750+44
3 Nov 2026, 00:1729,706+58
2 Nov 2026, 03:2829,648+116
1 Nov 2026, 04:0929,532+48
31 Oct 2026, 07:3529,484+61
30 Oct 2026, 09:0629,423+33
29 Oct 2026, 06:4929,390+34
28 Oct 2026, 04:3129,356+53
27 Oct 2026, 01:3729,303+5
26 Oct 2026, 02:4029,298+40
25 Oct 2026, 01:1829,258+64
24 Oct 2026, 02:0729,194+73
23 Oct 2026, 02:1029,121first reading

Engagement

43 posts held, back to 16 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 165 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.7%
avg views ÷ 30,371 subscribers
Avg views / post
5,670
10 posts measured
Reaction rate
0.136%
reactions ÷ views · ER floor
Posts in window
10
of 43 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 8 of 10 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 November 2026
Posts held43 (16 July 2026 – 14 November 2026)
Views total56,690
Reactions total63
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 02:02 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
264
Videos
66
Links
154

Lifetime counters from Telegram’s own channel header, read 17 November 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.

Video runtime
2m 22s
Average length
10s

Measured directly from 14 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.

Reaction mix

205 reactions across 36 posts, in 3 distinct kinds. The most used accounts for 96.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤19896.6%
👍62.93%
🥰10.488%

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

Measured over the 43 most recent posts we hold, published 16 July 2026 to 14 November 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: 3 of 10 posts held from the last 30 days (30.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).

14 Nov 2026, 17:48 UTC≈4,010 views8 reactionsread 17 November 2026
Photo

人照10分顶级炮架的服务系大奶高颜值御姐! 【老师花名】:#星拾壹 【出击次数】: 1刷/p 【上课费用】:1200P 【出击评价】:#超级好评 【老师特点】: #天生魅魔 #高颜值御姐 #被动大蟒蛇 #完美身材 #深喉不断 #duangduang臀 【老师车牌】 @wenxudad 简报请点击查看👇👇👇 #硬件配置∶ 165身高,50kg左右, 皮肤光滑,无赘肉,白皮,D杯水滴型奶,手感绵软,乳头粉色,乳晕正常大小 人照10分(参考视频),高颜值御姐狐狸脸,摄人心魄,精致高级! 浅褐色小蝴蝶,毛量正常。腰臀比优秀,臀部为小肥臀,饱满有肉感,后入撞击臀浪翻滚。 #服务内容 【陪浴】:搓三点 【水中萧】:深喉到底,眼神妩媚撩人 【按摩】:基础款 【毒龙】:基础款无顶肛 【口交】:略有齿感,包裹强,高强度深喉到底,时间持久! 【舌吻】:被动大蟒蛇,要就给,管饱! 【潮喷】:老A太菜,没凿喷~遗憾~ #服务态度 拉满,…

❤7👍1

9 Nov 2026, 15:39 UTC≈5,460 views8 reactionsread 17 November 2026
Photo

大奶大蟒蛇深喉冷白皮BBW的新疆谷爱玲! 【老师花名】:#麦迪小蛋糕 #新疆 【出击次数】: 1刷/p 【上课费用】:1000P 【出击评价】:#超级好评 【老师特点】: #神似谷爱玲 #丰乳肥臀E奶 #主动大蟒蛇 #冷白皮 #西域艳后 #深喉不断 #duangduang臀 【老师车牌】 @xiaodangaommaidi 简报请点击查看👇👇👇 #硬件配置∶ 165身高,55kg左右,丰乳肥臀,微胖型BBW 皮肤一般,有点小肚子,冷白皮,比我还白好多~纯天然E杯,外扩硕大木瓜奶,手感绵软,乳头粉红色且偏小,极其敏感,乳晕颜色很淡,自然状态就会凸起,刺激后会充血变硬。 人照9分,本人妆容精致不卡粉,神似谷爱玲,异域风情! 腰臀比优秀,臀部为欧美款性感大肥臀,饱满有肉感,后入撞击臀浪翻滚。 无69项目未观察户型. #服务内容 【陪浴】:搓三点 【口交】:丝滑,无齿感,包裹强,高强度深喉到底,时间持久! 【乳胶】:巨乳…

❤8

9 Nov 2026, 09:56 UTC≈4,570 viewsread 17 November 2026

新月老师炸号了 新号 @xinyuels12 双向 @xsodhabot

9 Nov 2026, 03:06 UTC≈3,550 views3 reactionsread 17 November 2026
Forwarded from @alexteamreportPhoto

👩‍🦰【品牌】:#桃花坞硅胶娃娃体验馆 ☎️【联系】: @taohuajiejie ⚠️【提示】:#商家 #硅胶娃娃 #新奇体验 ❤️‍🔥桃花坞新奇体验馆❤️‍🔥 🥰一个懂男人的专业服务馆、主营日本进口高级性爱娃娃体验 、主打新奇➕刺激 体验感直接拉满🔥 全杭州各区域有门店24小时接单、私信客服匹配就近门店安排体验。 🥳新奇体验超刺激➕超强夹吸➕云柔酥胸➕无限火力❤️‍🔥 #硅胶娃娃 #无限火力 #杭州全区 客服:@taohuajiejie 群聊:@Y886607 频道:@Y88660702 微信:Y88660702

❤3

6 Nov 2026, 19:23 UTC≈6,100 views8 reactionsread 17 November 2026
Photo

拥有吸盘逼冷白皮三点粉神似李沁的大蟒蛇大奶颜值御姐!(10天之前的上榜照片有点太过朴素,差点错过!) 【老师花名】:#湉湉 【出击次数】: 1刷/p 【上课费用】:1300P 【出击评价】:#超级好评 【老师特点】: #神似李沁和高圆圆 #细支硕果 #吸盘逼屌感劲爆 #主动大蟒蛇 #冷白皮 #真胸圆盘C奶 #敏感体质 #完美炮架 【老师车牌】 @tiantian50408 简报请点击查看👇👇👇 #硬件配置∶ 160左右身高,48kg左右,小只马 皮肤光滑水嫩,全身无多余赘肉,冷白皮,纯天然C杯挺拔圆盘奶,饱满圆润有弹性,手感绵软,乳头粉褐色,较为敏感,自然状态就会凸起,刺激后会充血变硬。 人照9分,本人比照片好看不少,照片反而显得一般,侧脸有点像李沁和高圆圆,群里狼友说像七森莉莉!(七森莉莉是谁,我不认识啊!) 腰臀比优秀,臀部为性感小肥臀,饱满有肉感,后入撞击臀浪翻滚。 户型为粉褐色小蝴蝶,毛量正常,敏感体质,章鱼吸盘…

❤7👍1

5 Nov 2026, 05:50 UTC≈6,480 views8 reactionsread 17 November 2026
Photo

天生可爱娃娃音的敏感体质屌感劲爆的大奶高颜值嫩妹! 【老师花名】:#月栖奈 【出击次数】: 1刷/p 【上课费用】:900P 【出击评价】:#接近超级好评 【老师特点】: #娃娃音萝莉 #细支硕果 #屌感劲爆 #真胸水滴C奶 #敏感体质 【老师车牌】 @wanwan16852 简报请点击查看👇👇👇 #硬件配置∶ 160左右身高,44kg左右,小只马,抽烟 皮肤光滑水嫩,全身无多余赘肉,黄皮,手臂,胸口,大腿均有符文,纯天然C杯水滴奶,饱满圆润有弹性,手感绵软,乳头浅褐色,较为敏感,刺激乳头会充血凸起,乳晕收缩皱起。 人照12分,本人比照片好看很多,请参考验证视频。 腰臀比优秀,臀部为性感小翘臀,饱满有肉感,后入撞击臀浪翻滚。 户型为褐色小蝴蝶,毛量正常,敏感体质~ #服务内容 【陪浴】:打泡沫后胸推+臀推(此为老A现场调教内容,或可加入正式课表!) 【口交】:丝滑,无齿感,包裹强,吃鸡高手! 【69】:生理期快来不方…

❤8

3 Nov 2026, 18:52 UTC≈5,680 views9 reactionsread 14 November 2026
Photo

1️⃣0️⃣ 月好评报告排行榜 为了方便新加群的狼友选择靠谱的口碑老师,同时激励老师提升客户体验,特举办报告好评排行榜活动 排行榜为老师花名加群内报告数,可点击蓝色字体查看老师榜单的详细内容 2️⃣ 贝贝29 3️⃣ 小小雨26 4️⃣ 知允25 5️⃣ 糯糯24 6️⃣ 木瓜瓜23 7️⃣ 思思22 8️⃣ 佳佳20 9️⃣ 绘梨衣19 1️⃣0️⃣ 大E学妹18 1️⃣1️⃣ 米米15 1️⃣2️⃣ 塞壬14 1️⃣3️⃣ 玥瑶13 1️⃣4️⃣ 文文12 林若萱12 1️⃣5️⃣ 饼干11 潮喷小柔11 蔓越莓11 1️⃣6️⃣ 符文贝贝10 1️⃣7️⃣ 贝儿9 鑫鑫9 怡怡9 梓琪9 乐煊…

❤9

31 Oct 2026, 05:43 UTC≈7,200 views8 reactionsread 9 November 2026
Photo

发完第二天就红休了,重发一下!这不是我造成的🥹 白皮小只马,敏感健身姬,一字马搭配果冻臀,榨精好手!!! 【老师花名】:#新月 【出击次数】: 1刷/p 【上课费用】:900P 【出击评价】:#接近超级好评 【老师特点】:#敏感体质 #一字马 #果冻臀 #可爱女友感 #白皮小只马 #女上桩机全自动 【老师车牌】: @xyue1 简报请点击查看👇👇👇 #硬件配置∶ 158左右身高,44kg左右,小只马, 皮肤光滑,全身无多余赘肉,黄白皮,无符文,C杯圆盘奶有科技底座,外扩胸型,饱满圆润有弹性,手感紧密,乳头浅褐色,较为敏感,刺…

❤8

24 Oct 2026, 11:51 UTC≈5,790 viewsread 9 November 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_103348032

23 Oct 2026, 17:10 UTC≈7,850 views11 reactionsread 9 November 2026
Video

敏感体质屌感爆棚的F奶嫩妹! 【老师花名】:#夏糯糯 【出击次数】: 1刷/p 【上课费用】:1500P 【出击评价】:#接近超级好评 【老师特点】: #女上桩机 #细支硕果 #屌感劲爆 #真胸F奶 #敏感体质 【老师车牌】 @bsbsjj_jaj 简报请点击查看👇👇👇 #硬件配置∶ 164身高,45kg,19岁。 身材比例很好,细支硕果,全身无赘肉,黄皮,皮肤一般,无体味。 纯天然腺体胸F杯, 饱满挺拔木瓜型,手感Q弹,乳晕大乳头浅正常大小,为褐色。胸和乳头摸起来很软嫩有弹性,乳头自然状态平,刺激后会竖起。 人照9分,对比照片有点美颜,头很小,脸部妆容比身体白一个色号,属于邻家小美女。 小穴为人工白虎小馒头,下面很紧润,水很多,玩玩奶子就开始流水了 。 腰臀比很棒,臀部为肉感duangduang臀,肉都长在了胸和屁股上面了! #服务内容 【陪浴】:搓三点,还加了洗背 【水中萧】:丝滑无齿感包裹性强,可惜无法深喉,老师…

❤8👍3

18 Oct 2026, 05:43 UTC≈10,100 views5 reactionsread 9 November 2026
Photo

白皮大奶颜值御姐,口活丝滑,逼逼夹得很紧!!! 【老师花名】:#小小苏 【出击次数】: 1刷/p 【上课费用】:1000P 【出击评价】:#接近超级好评 【老师特点】:#敏感体质 #丰乳肥臀 #夹紧逼 #颜值御姐 #白皮大车 #丝滑口活 【老师车牌】: @xxsxxs18 简报请点击查看👇👇👇 #硬件配置∶ 170左右身高,52kg左右,高个御姐, 皮肤光滑,全身无多余赘肉,黄白皮,无符文,C杯水滴奶,饱满圆润有弹性,手感紧密,乳头浅褐色,较为敏感,刺激会充血凸起。人照9分,本人比照片好看,有点日韩女星的感觉。现场妆容需要提…

❤5

5 Oct 2026, 11:53 UTC≈8,800 views5 reactionsread 9 November 2026
Photo

一旦老师出现高额定金(超过100-200),还有盲盒活动,请及时找群主管理确认老师账号情况,大概率是骗子盗号骗钱,请大家一定保护好自己的财产安全!!!

❤5

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

Posts edited after publishing

@whyalexalways1234 edited 3 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.

First edit seen
8 August 2026
Most recent edit
11 November 2026

Posts recorded as deleted after publishing

We recorded 6 posts on @whyalexalways1234 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
29 August 2026
Most recent seen missing
31 October 2026
Median time before seen missing
10 days
Seen missing in the last 30 days
2

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 4 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.

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

“杭州Alex总是123” (@whyalexalways1234), 30,371 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/whyalexalways1234.

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.