Telegram RegisterThe public register of Telegram
Telegram profile photo for 涩涩基地|推特|网红|福利

Channel

涩涩基地|推特|网红|福利

@Lovese4

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

14,227subscribers

+14,192 since we began measuring on 24 August 2026

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

Register entry

Telegram ID-1003993166523
TypeChannel
Username@Lovese4
CreatedBetween 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 September 2026
Last confirmed live19 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/Lovese4

Topic

Adult — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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

3514,2277,13124 August 2026 — 35 subscribers25 August 2026 — 137 subscribers2 September 2026 — 683 subscribers10 September 2026 — 4,312 subscribers10 September 2026 — 4,312 subscribers14 September 2026 — 9,128 subscribers19 September 2026 — 14,227 subscribers24 August 202619 September 2026
7 measurements spanning 26 days, net +14,192. 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 subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 14:3614,227+5,099
14 Sept 2026, 21:029,128+4,816
10 Sept 2026, 23:214,312no change
10 Sept 2026, 23:184,312+3,629
2 Sept 2026, 13:08683+546
25 Aug 2026, 13:03137+102
24 Aug 2026, 14:4535first 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“涩涩基地|推特|网红|福利” (@Lovese4), 14,227 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Lovese4.

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.