![Telegram profile photo for ⚥ HFC - Lightcore [ Sweetie Furry ] ⚥](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMzIwIiBoZWlnaHQ9IjMyMCIgcHJlc2VydmVBc3BlY3RSYXRpbz0ibm9uZSIgdmlld0JveD0iMCAwIDEwMCAxMDAiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyI%2BPGRlZnM%2BPGxpbmVhckdyYWRpZW50IGlkPSJnIiB4MT0iMCUiIHgyPSIwJSIgeTE9IjAlIiB5Mj0iMTAwJSI%2BPHN0b3Agb2Zmc2V0PSIwJSIgc3RvcC1jb2xvcj0iI2UwYTJmMyIvPjxzdG9wIG9mZnNldD0iMTAwJSIgc3RvcC1jb2xvcj0iI2Q2NjllZCIvPjwvbGluZWFyR3JhZGllbnQ%2BPC9kZWZzPjxzdHlsZT50ZXh0e2ZvbnQ6NjAwIDQ0cHggLWFwcGxlLXN5c3RlbSxCbGlua01hY1N5c3RlbUZvbnQsJ1NlZ29lIFVJJyxSb2JvdG8sSGVsdmV0aWNhLEFyaWFsLHNhbnMtc2VyaWYsJ0FwcGxlIENvbG9yIEVtb2ppJywnU2Vnb2UgVUkgRW1vamknLCdTZWdvZSBVSSBTeW1ib2wnOy13ZWJraXQtdXNlci1zZWxlY3Q6bm9uZTt1c2VyLXNlbGVjdDpub25lfTwvc3R5bGU%2BPHJlY3Qgd2lkdGg9IjEwMCIgaGVpZ2h0PSIxMDAiIGZpbGw9InVybCgjZykiLz48dGV4dCB0ZXh0LWFuY2hvcj0ibWlkZGxlIiB4PSI1MCIgeT0iNjYiIGZpbGw9IiNmZmYiPkhGPC90ZXh0Pjwvc3ZnPg%3D%3D)
Channel
⚥ HFC - Lightcore [ Sweetie Furry ] ⚥
@hfc_light
On this record: Topic · Growth · Engagement · Cite this entry
1,371subscribers
-17 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001363090441 |
|---|---|
| Type | Channel |
| Username | @hfc_light |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 September 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 2 times, most recently 12 October 2026 |
| On Telegram | t.me/hfc_light |
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 30 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 13:14 | 1,371 | -2 |
| 30 Sept 2026, 17:02 | 1,373 | no change |
| 27 Sept 2026, 15:00 | 1,373 | -5 |
| 12 Sept 2026, 01:57 | 1,378 | -1 |
| 7 Sept 2026, 14:37 | 1,379 | +2 |
| 2 Sept 2026, 08:43 | 1,377 | -2 |
| 29 Aug 2026, 23:28 | 1,379 | +1 |
| 26 Aug 2026, 16:07 | 1,378 | -3 |
| 19 Aug 2026, 18:42 | 1,381 | -2 |
| 16 Aug 2026, 08:36 | 1,383 | -4 |
| 10 Aug 2026, 06:30 | 1,387 | -1 |
| 6 Aug 2026, 20:38 | 1,388 | 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.
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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“⚥ HFC - Lightcore [ Sweetie Furry ] ⚥” (@hfc_light), 1,371 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/hfc_light.
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.