Telegram RegisterThe public register of Telegram

Channel

Tales by moon light🌙

@crackjok

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

35subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002237456004
TypeChannel
Username@crackjok
DescriptionStories that brings back old time momeries
CreatedBetween 1 June 2024 and 7 July 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/crackjok

Growth

357 August 2026 — 35 subscribers10 August 2026 — 35 subscribers7 August 202610 August 2026
2 measurements spanning 3 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 34–36 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 23:3135no change
7 Aug 2026, 12:5535first reading

Engagement

19 posts held, back to 7 July 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 14 July 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
20
Links
23

Lifetime counters from Telegram’s own channel header, read 10 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.

Recent posts

14 Jul 2024, 12:32 UTC60 viewsread 10 August 2026
Forwarded from @belevskmovePhoto

📣 Hamster kombAt 13.07 📣 @hamster_kombAt 1. Буква T: — 2. Буква R: • — • 3. Буква U: • • — 4. Буква S: • • • 5. Буква T: —

14 Jul 2024, 12:06 UTC50 viewsread 10 August 2026
Forwarded from @podarkihamsterPhoto

📣 Hamster kombAt 14.07 📣 kombo @hamster_kombAt

13 Jul 2024, 19:27 UTC41 viewsread 10 August 2026
Forwarded from @podarkihamsterPhoto

📣 Hamster kombAt 13.07 📣 @hamster_kombAt 1. Буква T: — 2. Буква R: • — • 3. Буква U: • • — 4. Буква S: • • • 5. Буква T: —

13 Jul 2024, 19:06 UTC32 viewsread 10 August 2026
Photo

⚡️ TapSwap has a new task in the "Cinema" section You will receive 200,000 TapSwap coins for completing the task. 1️⃣ Today’s code to activate the first task is "4K7U6E10G7" 2️⃣ Сode to activate the second task is "tardigrade" ‼️It is important to know that you can activate the code only after watching the video on TapSwap channel! PLAY TAPSWAP –> https://t.me/tapswap_mirror_bot?start=r_84131214 Tap-To-Earn:

13 Jul 2024, 09:20 UTC21 viewsread 10 August 2026
Forwarded from @podarkihamsterPhoto

📣 PixelTap 13.07 📣 Combo @pixelversexyzbot

12 Jul 2024, 19:59 UTC22 viewsread 10 August 2026
Forwarded from @podarkihamsterPhoto

📣 Hamster kombAt 12.07 📣 @hamster_kombAt 1. Буква B: — • • • 2. Буква L: • — • • 3. Буква O: — — — 4. Буква C: — • — • 5. Буква K: — • —

12 Jul 2024, 12:10 UTC19 viewsread 10 August 2026
Forwarded from @podarkihamsterPhoto

📣 Hamster kombAt 12.07 📣 kombo @hamster_kombAt

12 Jul 2024, 09:02 UTC19 viewsread 10 August 2026
Forwarded from @podarkihamsterPhoto

📣 PixelTap 12.07 📣 kombo @pixelversexyzbot

11 Jul 2024, 19:25 UTC21 viewsread 10 August 2026
Forwarded from @podarkihamsterPhoto

📣 Hamster kombAt 11.07 📣 @hamster_kombAt N - . O - - - D - . . E . S . . .

11 Jul 2024, 16:46 UTC21 viewsread 10 August 2026
Forwarded from @podarkihamsterPhoto

📣 PixelTap 11.07 📣 kombo @pixelversexyzbot

11 Jul 2024, 12:25 UTC25 viewsread 10 August 2026
Forwarded from @podarkihamsterPhoto

📣 Hamster kombAt 11.07 📣 kombo @hamster_kombAt

Showing the 12 most recent of 19 posts we hold for @crackjok. 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

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

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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“Tales by moon light🌙” (@crackjok), 35 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/crackjok.

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.