Supergroup

福利群jisou🔞

@xinshijiefuli56

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

140members

+82 since we began measuring on 8 August 2026

7 online right now

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

Register entry

Telegram ID	-1003900224025
Type	Supergroup
Username	@xinshijiefuli56
Description	廣告聯繫：https://t.me/junyu888888 線上娛樂開戶：https://t.me/junyu888888 🈲止發暴力血腥類視頻話題声明视频部分为转载！！
Created	Between 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	17 October 2026
Last confirmed live	18 October 2026
Measurements held	9
On Telegram	t.me/xinshijiefuli56

Topic

Gambling & betting — 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 17 October 2026 and assigned it the closest of 31 fixed categories, at 69% 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

9 measurements spanning 71 days, net +82. 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 46–152 and does not start at zero.

Measurement log — every members count we have recorded
Measured (UTC)	Members	Change
17 Oct 2026, 18:56	140	no change
1 Oct 2026, 14:02	140	+21
16 Sept 2026, 00:20	119	+12
8 Sept 2026, 01:58	107	+18
30 Aug 2026, 13:44	89	+12
24 Aug 2026, 12:04	77	+11
17 Aug 2026, 10:47	66	+6
9 Aug 2026, 02:31	60	+2
8 Aug 2026, 03:51	58	first 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 57 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“福利群jisou🔞” (@xinshijiefuli56), 140 members as measured 17 October 2026. Telegram Register, tgregister.com/channel/xinshijiefuli56.

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.