Telegram RegisterThe public register of Telegram
Telegram profile photo for 福利姬摩多 收藏夹

Channel

福利姬摩多 收藏夹

@freefuliji

Has discussion group2 usernames

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

350,113subscribers

+35 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 316,228–1,000,000.

Register entry

Telegram ID-1001868806587
TypeChannel
Usernames@freefuliji @me800
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 August 2026
Measurements held18
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/freefuliji

Topic

Other / unclassifiable — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 50% 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

350,030350,113350,071.57 August 2026 — 350,078 subscribers7 August 2026 — 350,078 subscribers8 August 2026 — 350,059 subscribers8 August 2026 — 350,068 subscribers9 August 2026 — 350,100 subscribers9 August 2026 — 350,110 subscribers9 August 2026 — 350,104 subscribers10 August 2026 — 350,111 subscribers10 August 2026 — 350,084 subscribers11 August 2026 — 350,074 subscribers12 August 2026 — 350,052 subscribers12 August 2026 — 350,055 subscribers12 August 2026 — 350,044 subscribers12 August 2026 — 350,044 subscribers14 August 2026 — 350,030 subscribers14 August 2026 — 350,031 subscribers15 August 2026 — 350,110 subscribers15 August 2026 — 350,113 subscribers7 August 202615 August 2026
18 measurements spanning 8 days, net +35. 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 350,018–350,125 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 18:48350,113+3
15 Aug 2026, 17:22350,110+79
14 Aug 2026, 08:26350,031+1
14 Aug 2026, 07:33350,030-14
12 Aug 2026, 22:53350,044no change
12 Aug 2026, 22:33350,044-11
12 Aug 2026, 02:03350,055+3
12 Aug 2026, 01:32350,052-22
11 Aug 2026, 03:16350,074-10
10 Aug 2026, 23:43350,084-27
10 Aug 2026, 01:51350,111+7
9 Aug 2026, 22:31350,104-6
9 Aug 2026, 03:11350,110+10
9 Aug 2026, 00:54350,100+32
8 Aug 2026, 05:38350,068+9
8 Aug 2026, 03:53350,059-19
7 Aug 2026, 18:42350,078no change
7 Aug 2026, 08:50350,078first reading

Engagement

No public post preview. We read this entry on 7 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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

“福利姬摩多 收藏夹” (@freefuliji), 350,113 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/freefuliji.

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.