8 Aug 2026, 18:21 UTCviews —
𝔑𝔢𝔞𝔡𝔶 ℑ𝔬 ᷤ ⷩ ⷪⷪ ⷪ ͭ pinned a photo
Channel
𝔑𝔢𝔞𝔡𝔶 ℑ𝔬 ᷤ ⷩ ⷪⷪ ⷪ ͭ
@lREADY_TO_SHOOT
On this record: Growth · Engagement · Posts · Citations · Cite this entry
140subscribers
-30 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002935209790 |
|---|---|
| Type | Channel |
| Username | @lREADY_TO_SHOOT |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/lREADY_TO_SHOOT |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 02:21 | 140 | -4 |
| 1 Sept 2026, 16:14 | 144 | -6 |
| 24 Aug 2026, 21:24 | 150 | -12 |
| 16 Aug 2026, 09:03 | 162 | -56 |
| 9 Aug 2026, 09:52 | 218 | +48 |
| 8 Aug 2026, 21:00 | 170 | no change |
| 8 Aug 2026, 20:47 | 170 | first reading |
Engagement
19 posts held, back to 2 August 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 19 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
8 Aug 2026, 16:26 UTC15 viewsread 8 August 2026
Sticker
Sticker, posted without a caption
8 Aug 2026, 11:46 UTC133 viewsread 8 August 2026
Tell me why. Tell me why. Late night on a fading line. Your voice fee so far this time. Saying words, but they don't align. Something's breaking out of sight. We were fire, we were it's quiet, getting cold. gold, now Every truth we never told turns. The stories get old Every truth we never told turns. The stories getting old. Don't turn. Don't hide. I can see it in your eyes. Tell me why. Tell me why we got l…
Signed 𝛢Ꮴ𝛪𝛮
8 Aug 2026, 11:46 UTC130 viewsread 8 August 2026
File
File, posted without a caption
Signed 𝛢Ꮴ𝛪𝛮
8 Aug 2026, 11:46 UTC33 viewsread 8 August 2026
Sticker
Sticker, posted without a caption
8 Aug 2026, 11:46 UTC129 viewsread 8 August 2026
Photo
+ تو هیچوقت عاشق شدی؟ خاکستری نگاهم کرد. خاکستری، غمگین ترینِ رنگهاست!
Signed 𝛢Ꮴ𝛪𝛮
8 Aug 2026, 11:46 UTC74 viewsread 8 August 2026
ــــــــتـمامش بهخـاطر حس کردن کمی 'دوستداشتـهشدن' بـود؟
8 Aug 2026, 11:04 UTC31 viewsread 8 August 2026
Sticker
Sticker, posted without a caption
8 Aug 2026, 00:07 UTC28 viewsread 8 August 2026
Sticker
Sticker, posted without a caption
8 Aug 2026, 00:00 UTC28 viewsread 8 August 2026
Sticker
Sticker, posted without a caption
7 Aug 2026, 23:59 UTC20 viewsread 8 August 2026
Forwarded from @jrexdkPhoto
˓ 𝚴𝖺𝗆ꤕ ˒ 𝖢𝖺𝗌𝖾 𝖱-𝟣𝟥 / 𝖱-𝟣𝟥 پرونده 𝖯𝖺𝗋𝗍 𝟩 𝖦𝖾𝗇𝗋𝖾 : 𝖠𝖼𝗍𝗂𝗈𝗇,𝖢𝗋𝗂𝗆𝗂𝗇𝖺𝗅,𝖾𝗑𝖼𝗂𝗍𝗂𝗇𝗀, 𝗉𝖺𝗋𝖺𝖽𝗈𝗑𝗂𝖼𝖺𝗅,𝖱𝗈𝗆𝖺𝗇𝗍𝗂𝖼, 𝖡𝖫 𝖤𝗑𝗉𝗅𝖺𝗇𝖺𝗍𝗂𝗈𝗇𝗌 : 𝗞𝗼𝗼𝗸𝘃 — 𝖠 𝗌𝗎𝗌𝗉𝖾𝗇𝗌𝖾𝖿𝗎𝗅 𝗍𝖺𝗅𝖾 𝖻𝗎𝗋𝗂𝖾𝖽 𝖽𝖾𝖾𝗉 𝗐𝗂𝗍𝗁𝗂𝗇 𝖺 𝗐𝗈𝗋𝗅𝖿 𝗈𝖿 𝗌𝖾𝖼𝗋𝖾𝗍𝗌,𝗆𝗒𝗌𝗍𝖾𝗋𝗒,𝖺𝗇𝖽 𝖻𝗅𝗈𝗈𝖽𝗌𝗁𝖾𝖽. 𝖳𝖠𝖯 𝖳𝖮 𝖱𝖤𝖠𝖣 𝖳𝖧𝖤 𝖲𝖳𝖮𝖱𝖸 𝖠𝗎𝗍һ꤀г : 𝚪꤀𝗆𝖺𐔓 , 𝖢𝗁𝖺𝗇𝗇𝖾𝗅
7 Aug 2026, 14:07 UTC26 viewsread 8 August 2026
Sticker
Sticker, posted without a caption
Showing the 12 most recent of 19 posts we hold for @lREADY_TO_SHOOT. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Mentions
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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“𝔑𝔢𝔞𝔡𝔶 ℑ𝔬 ᷤ ⷩ ⷪⷪ ⷪ ͭ” (@lREADY_TO_SHOOT), 140 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/lREADY_TO_SHOOT.
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.