Telegram RegisterThe public register of Telegram
Telegram profile photo for 🪼《NEW全网担保资源探讨交流会》入口

Supergroup

🪼《NEW全网担保资源探讨交流会》入口

@baikedb

Has discussion group

On this record: Topic · Growth · Engagement · Citations · Cite this entry

835members

-2,922 since we began measuring on 18 September 2026

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

Register entry

Telegram ID-1002264308290
TypeSupergroup
Username@baikedb
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 September 2026
Last confirmed live2 November 2026
Measurements held7
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/baikedb

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 13 October 2026 and assigned it the closest of 31 fixed categories, at 90% 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

923,7571,924.518 September 2026 — 3,757 members18 September 2026 — 3,757 members1 October 2026 — 92 members12 October 2026 — 524 members18 October 2026 — 659 members26 October 2026 — 828 members2 November 2026 — 835 members83518 September 20262 November 2026
7 measurements spanning 45 days, net -2,922. 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”.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
2 Nov 2026, 09:28835+7
26 Oct 2026, 09:38828+169
18 Oct 2026, 19:46659+135
12 Oct 2026, 12:49524+432
1 Oct 2026, 05:1592-3,665
18 Sept 2026, 21:273,757no change
18 Sept 2026, 20:473,757first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

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

“🪼《NEW全网担保资源探讨交流会》入口” (@baikedb), 835 members as measured 2 November 2026. Telegram Register, tgregister.com/channel/baikedb.

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.