Telegram RegisterThe public register of Telegram
Telegram profile photo for 濮阳恒丰万嘉外围

Channel

濮阳恒丰万嘉外围

@Pydalikaiche

On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

999subscribers

-5 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003978834553
TypeChannel
Username@Pydalikaiche
CreatedBetween 1 April 2026 and 20 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/Pydalikaiche

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

Growth

9991,0051,0026 August 2026 — 1,004 subscribers6 August 2026 — 1,004 subscribers19 August 2026 — 1,005 subscribers10 September 2026 — 1,003 subscribers14 September 2026 — 999 subscribers6 August 202614 September 2026
5 measurements spanning 38 days, net -5. 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 998–1,006 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 05:40999-4
10 Sept 2026, 14:371,003-2
19 Aug 2026, 17:241,005+1
6 Aug 2026, 20:031,004no change
6 Aug 2026, 19:511,004first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

1 Aug 2026, 07:30 UTC4 viewsread 6 August 2026
Photo

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

1 Aug 2026, 07:30 UTC3 viewsread 6 August 2026
Photo

【验证是否】: #濮阳 已验证 【编 号】: 9 【联系方式】:不欢迎口炮!支持U付款 联系群主👉 客 服:@MX_99999 被双向的联系 👉@puyangDaLiBot 【 地 址 】: 【修车水费】: 强烈建议带现金 【服务详情】: 【 优 缺 点 】: 【验证反馈】: 提示刚进群的新朋友: 1.我这里不白嫖,群内所有资源我不保证你随时加妹子随时同意,没人一直盯着手机;妹子有事两天不上号也是正常的,希望申请加的朋友耐心等待,如果长时间(5-7天)没同意再来找我 我每天都会抽时间上号。 2.还有就是私聊你卖资源的都是骗子!别看见发个妹子图片就不会思考了,看见这种及时举报以免被骗! 3.大半夜就别来找我了!不会为了几十块熬一夜的,别问一些低级问题 4.无论约谁必须见面给钱,车费自己商量。但凡没有见着面就给了钱被骗的就别吭气了,自己就当交学费了!

30 Jul 2026, 20:29 UTC3 viewsread 6 August 2026
Photo

【验证是否】: #濮阳 已验证 【编 号】: 8 【联系方式】:不欢迎口炮!支持U付款 联系群主👉 客 服:@MX_99999 被双向的联系 👉@puyangDaLiBot 【 地 址 】: 【修车水费】: 强烈建议带现金 【服务详情】: 【 优 缺 点 】: 【验证反馈】: 提示刚进群的新朋友: 1.我这里不白嫖,群内所有资源我不保证你随时加妹子随时同意,没人一直盯着手机;妹子有事两天不上号也是正常的,希望申请加的朋友耐心等待,如果长时间(5-7天)没同意再来找我 我每天都会抽时间上号。 2.还有就是私聊你卖资源的都是骗子!别看见发个妹子图片就不会思考了,看见这种及时举报以免被骗! 3.大半夜就别来找我了!不会为了几十块熬一夜的,别问一些低级问题 4.无论约谁必须见面给钱,车费自己商量。但凡没有见着面就给了钱被骗的就别吭气了,自己就当交学费了!

30 Jul 2026, 20:00 UTC4 viewsread 6 August 2026
Photo

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

29 Jul 2026, 00:54 UTC6 viewsread 6 August 2026
Photo

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

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

Mentions

Named by 9 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.

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.

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

“濮阳恒丰万嘉外围” (@Pydalikaiche), 999 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/Pydalikaiche.

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.