2 Jul 2025, 08:59 UTCviews —
Отзывы @NFTEzhik pinned «Теперь свои отзывы можете писать сюда👇»
Channel
Отзывы @NFTEzhik
@otzivyEzhika
On this record: Growth · Engagement · Posts · Citations · Cite this entry
6subscribers
+2 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002787370326 |
|---|---|
| Type | Channel |
| Username | @otzivyEzhika |
| Created | 23 June 2025 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/otzivyEzhika |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 12:58 | 6 | +2 |
| 13 Aug 2026, 07:01 | 4 | no change |
| 9 Aug 2026, 10:52 | 4 | first reading |
Engagement
14 posts held, back to 23 June 2025 — 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 14 posts for this entry, the most recent from 2 July 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
28 Jun 2025, 08:59 UTC120 viewsread 13 August 2026
Теперь свои отзывы можете писать сюда👇
27 Jun 2025, 08:46 UTC111 viewsread 13 August 2026
С 7 до 30 поднялся у тебя на халяве
27 Jun 2025, 08:38 UTC109 viewsread 13 August 2026
@NFTezhik не скам, первый открыл картинку - получил приз
26 Jun 2025, 17:49 UTC109 viewsread 13 August 2026
@NFTEzhik без скама, нфт залутала ❤️
26 Jun 2025, 10:44 UTC115 viewsread 13 August 2026
Сыграл в лудку, выиграл с 10 раза получил подарок профит +15 звезд спасибо все честно удачи администратору
25 Jun 2025, 07:30 UTC88 viewsread 13 August 2026
Спасибо @NFTEzhik все сделал чётко и быстро👍
24 Jun 2025, 20:35 UTC68 viewsread 13 August 2026
Спасибо @NFTEzhik все чётко 👍
24 Jun 2025, 18:26 UTC79 viewsread 13 August 2026
@NFTEzhik заебись крутой чел
23 Jun 2025, 21:09 UTC76 viewsread 13 August 2026
@NFTEzhik не скам
23 Jun 2025, 17:01 UTC65 viewsread 13 August 2026
@NFTEzhik не скам, выиграл у него медведя, все получил
23 Jun 2025, 17:00 UTCviews —
Channel photo updated
Showing the 12 most recent of 14 posts we hold for @otzivyEzhika. 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.
Mentions
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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“Отзывы @NFTEzhik” (@otzivyEzhika), 6 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/otzivyEzhika.
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.