Channel
Iᴠᴏʀʏ’s Lɪᴛᴛʟᴇ Wᴏʀʟᴅ 𐙚 ‧₊˚ ⋅
@eff_by_soaoya
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,021subscribers
-119 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001960246999 |
|---|---|
| Type | Channel |
| Username | @eff_by_soaoya |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/eff_by_soaoya |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 13:14 | 2,021 | -12 |
| 31 Oct 2026, 15:28 | 2,033 | -10 |
| 28 Oct 2026, 06:47 | 2,043 | -7 |
| 25 Oct 2026, 02:57 | 2,050 | -6 |
| 19 Oct 2026, 08:55 | 2,056 | -4 |
| 15 Oct 2026, 23:50 | 2,060 | +2 |
| 13 Oct 2026, 04:57 | 2,058 | -10 |
| 6 Oct 2026, 22:56 | 2,068 | -18 |
| 29 Sept 2026, 21:17 | 2,086 | -16 |
| 19 Sept 2026, 23:05 | 2,102 | no change |
| 19 Sept 2026, 15:21 | 2,102 | +2 |
| 15 Sept 2026, 08:20 | 2,100 | -4 |
| 11 Sept 2026, 20:58 | 2,104 | -10 |
| 7 Sept 2026, 05:16 | 2,114 | -15 |
| 2 Sept 2026, 12:02 | 2,129 | -7 |
| 30 Aug 2026, 13:07 | 2,136 | -1 |
| 24 Aug 2026, 15:39 | 2,137 | -3 |
| 23 Aug 2026, 18:01 | 2,140 | 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@Theme_by_eaintymm · 54,055
Telegram ranks this channel #1 of 17 here — alongside 16 others — read 23 August 2026
@Theme_Lina_Vibe · 22,231
Telegram ranks this channel #4 of 8 here — alongside 7 others — read 20 September 2026
@kawaii_themes · 18,981
Telegram ranks this channel #16 of 36 here — alongside 35 others — read 3 October 2026
@mytelegramthemes · 29,479
Telegram ranks this channel #25 of 36 here — alongside 35 others — read 8 September 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“Iᴠᴏʀʏ’s Lɪᴛᴛʟᴇ Wᴏʀʟᴅ 𐙚 ‧₊˚ ⋅” (@eff_by_soaoya), 2,021 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/eff_by_soaoya.
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.