5500 birr @nani_fashion1

Channel
WHICH ONE?
@fashionkilababe
On this record: Topic · Growth · Engagement · Posts · Cite this entry
3,382subscribers
-145 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001131481616 |
|---|---|
| Type | Channel |
| Username | @fashionkilababe |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/fashionkilababe |
Topic
Ecommerce storefront — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 17 Nov 2026, 15:35 | 3,382 | -4 |
| 12 Nov 2026, 03:16 | 3,386 | -6 |
| 7 Nov 2026, 23:08 | 3,392 | -5 |
| 4 Nov 2026, 10:47 | 3,397 | -5 |
| 1 Nov 2026, 11:37 | 3,402 | -2 |
| 29 Oct 2026, 12:44 | 3,404 | -5 |
| 26 Oct 2026, 10:09 | 3,409 | -4 |
| 23 Oct 2026, 02:28 | 3,413 | -9 |
| 20 Oct 2026, 03:10 | 3,422 | -6 |
| 17 Oct 2026, 13:48 | 3,428 | -4 |
| 11 Oct 2026, 13:01 | 3,432 | -12 |
| 4 Oct 2026, 18:42 | 3,444 | -12 |
| 25 Sept 2026, 01:36 | 3,456 | -10 |
| 16 Sept 2026, 09:36 | 3,466 | -5 |
| 12 Sept 2026, 17:37 | 3,471 | -2 |
| 8 Sept 2026, 10:59 | 3,473 | -11 |
| 3 Sept 2026, 10:22 | 3,484 | -5 |
| 31 Aug 2026, 06:23 | 3,489 | -2 |
| 28 Aug 2026, 06:34 | 3,491 | -10 |
| 25 Aug 2026, 02:12 | 3,501 | first reading |
Engagement
10 posts held, back to 25 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 10 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
4000 birr @nani_fashion1
5000 birr @nani_fashion1
1800 birr On hand ✅ @nani_fashion1
7500 birr @nani_fashion1
4500 birr @nani_fashion1
4500 birr Size 31-45 @nani_fashion1
800 birr On hand ✅ @nani_fashion1
4000 birr Size 35-40 @nani_fashion1
12000 birr @nani_fashion1
Showing the 10 most recent of 10 posts we hold for @fashionkilababe. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“WHICH ONE?” (@fashionkilababe), 3,382 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/fashionkilababe.
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.