Channel
@meowdelisa
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
150subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001504309802 |
|---|---|
| Type | Channel |
| Username | @meowdelisa |
| Created | Between 1 July 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/meowdelisa |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 11:58 | 150 | +1 |
| 9 Sept 2026, 23:40 | 149 | +1 |
| 30 Aug 2026, 16:29 | 148 | -1 |
| 23 Aug 2026, 14:14 | 149 | -1 |
| 8 Aug 2026, 19:46 | 150 | no change |
| 6 Aug 2026, 23:47 | 150 | first reading |
11 posts held, back to 4 June 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 11 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
147 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 27.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5359443943534633873 | 41 | 27.9% | |
| custom 5017161103315043247 | 29 | 19.7% | |
| custom 5361967838116453579 | 28 | 19.0% | |
| custom 5357537970192661526 | 26 | 17.7% | |
| custom 5361802907077323970 | 10 | 6.80% | |
| custom 6247020835291273835 | 10 | 6.80% | |
| custom 5361909619834755990 | 3 | 2.04% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 11 of the 11 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 147 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 4 June 2026 to 5 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Музыка это конечно круто, но помимо нового микрофона я хочу себе камеру, коптер, и вести тревел блог, пока что есть только палатка нахуй, ну ничего
custom 53594439435346338737custom 50171611033150432474custom 53575379701926615263
Тяжелый был выбор между золотым яблоком и кемпингом, но я выбрала быть счастливой;) Схожу ли я в поход? Ага, обязательно, но хотя бы на озеро я точно съезжу, ну или просто в Чибит одна уеду и все
custom 53594439435346338736custom 53575379701926615265custom 62470208352912738355
такой сегодня вайбик
custom 53619678381164535797custom 53594439435346338734custom 53575379701926615263custom 50171611033150432471
delisa - DOMIK (version 2.0) prod. by probelad, xcomeer m&m - xcomeer sup - CEPHALON СЛУШАТЬ 🎧 СЛУШАТЬ 🎧 СЛУШАТЬ 🎧
custom 53594439435346338737custom 53619678381164535797custom 50171611033150432475custom 53575379701926615262
Пофоткались на обложку для трека «домик», пускай будет новая вавка и новая обложка
custom 53618029070773239707custom 53575379701926615263custom 53594439435346338732
Перезаписала наконец-то трек "домик", щас Даня сведет и заменю вавку на площадках🐈⬛🎧
custom 53594439435346338733custom 50171611033150432472custom 53575379701926615262
Пока что хватило сил доехать посмотреть на реку, следующий раз я уже искупаюсь иначе начну убивать
custom 53619678381164535798custom 50171611033150432473custom 53619096198347559902
84 крутка, я бы наложила себе в руки, если бы проиграла 50/50
custom 53575379701926615265custom 50171611033150432472custom 53594439435346338732
дальше меньше что уж
custom 53619678381164535795custom 62470208352912738355
два балбеса🐱
custom 50171611033150432478custom 53594439435346338735custom 53575379701926615263custom 53619678381164535791
delisa - связаны m&m / prod. by xcomeer sup - CEPHALON СЛУШАТЬ🤩
custom 53594439435346338735custom 50171611033150432474custom 53618029070773239703custom 53619096198347559901
Showing the 11 most recent of 11 posts we hold for @meowdelisa. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
“♱ delisa ♱” (@meowdelisa), 150 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/meowdelisa.
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.