ΠΡΠ΅Π½ΠΊΡ Π±ΠΈΡΡΡΡΡΓ«
Signed πππ_ππππ056π

Channel
@shikmedi
On this record: Growth Β· Engagement Β· What this channel posts Β· Posts Β· Citations Β· Cite this entry
8subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of Under 1,000.
| Telegram ID | -1003881597311 |
|---|---|
| Type | Channel |
| Username | @shikmedi |
| Created | Between 1 February 2026 and 1 March 2026 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/shikmedi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 15:16 | 8 | no change |
| 7 Aug 2026, 19:15 | 8 | first reading |
14 posts held, back to 1 March 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 14 posts for this entry, the most recent from 24 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegramβs own channel header, read 12 August 2026 β not the date at the top of this page, which is when the subscriber count was last read. Below Telegramβs rounding threshold, so these counts are exact.
Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel β not this channelβs whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegramβs own rounded chrome, so it carries no β mark.
ΠΡΠ΅Π½ΠΊΡ Π±ΠΈΡΡΡΡΡΓ«
Signed πππ_ππππ056π
ΠΠΎΠ΄ΠΏΠ΅ΡΠΈΡΠ΅ΡΡ ΠΏΠΆ ΠΏΠΆ
Signed πππ_ππππ056π
https://t.me/fig_tebe056
Signed πππ_ππππ056π
Channel photo updated
Posted without readable text
ΠΠ΅ΠΊΠ°Π±Π° Ρ ΡΠ΅Π³Π°Π½ΠΎΠΌ
Signed SHIKM
ΠΠΎΠ»ΠΎΠ΄Π΅Ρ ΡΡΠΎ ΠΠΎΠ»Π΄
Signed SHIKM
Π’ΠΎΠΊΠΎ ΠΊΠ°Π»Π΅Π±ΡΠΎΠ²ΠΊΡ Π·Π°Π²Π΅ΡΡΠΈΠ»
Signed πππ_ππππ056π
Video, posted without a caption
Signed πππ_ππππ056π
Video, posted without a caption
Signed πππ_ππππ056π
Π ΡΡΠ°Π·Ρ ΠΏΡΠΎΡΡΠ°Π»
Signed πππ_ππππ056π
Photo, posted without a caption
Signed πππ_ππππ056π
Showing the 12 most recent of 14 posts we hold for @shikmedi. 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.
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 12 August 2026 β this entry's latest reading, not the date you are reading this.
βSHIKM editors π«§β (@shikmedi), 8 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/shikmedi.
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.