Telegram RegisterThe public register of Telegram
Telegram profile photo for अच्छा बच्चा Avi Shukla

Channel

अच्छा बच्चा Avi Shukla

@busyAvi

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

33subscribers

+0 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-1001520669037
TypeChannel
Username@busyAvi
DescriptionBhulai nhi ja sakengyi wo yadein Yakeeen mano bahut yaad ayengy 🥹🥀🖤 ____ @aviXinfo❤️ @aviXlove😌 @iavishukla Avi - @iavishukla
CreatedBetween 1 August 2021 and 22 August 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/busyAvi

Growth

339 Aug 2026, 20:16 — 33 subscribers11 Aug 2026, 01:46 — 33 subscribers9 Aug 2026, 20:1611 Aug 2026, 01:46
2 measurements spanning 1 day. 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 32–34 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 01:4633no change
9 Aug 2026, 20:1633first reading

Engagement

20 posts held, back to 22 August 2022the 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 20 posts for this entry, the most recent from 29 June 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
2
Videos
4
Links
5

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

Video runtime
7s
Average length
7s

Measured directly from 1 video 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.

Reaction mix

2,133 reactions across 20 posts, in 25 distinct kinds. The most used accounts for 19.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍41819.6%
🔥38117.9%
28113.2%
🥰25111.8%
🤩1808.44%
👏1517.08%
😢1386.47%
👎1185.53%
😱723.38%
🤯391.83%
🤬301.41%
🕊221.03%
🎉140.656%
😁140.656%
❤‍🔥60.281%
💔40.188%
🤮30.141%
💋20.094%
😍20.094%
🤔20.094%
5 further kinds50.234%

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 20 of the 20 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 2,133reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 22 August 2022 to 29 June 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

29 Jun 2024, 17:23 UTC≈9,120 views19 reactionsread 11 August 2026
Video

Kisi shaam mujhe bhi yaad kar liya karo, Main dost purana hi sahi magar zinda hun :) Waqt ke saaye mein, humne bhi kuch pal bitaye hain, Dosti ke is safar mein, humne bhi rang sajaaye hain Tanhaayi ki dhund mein, khud ko bhool na jaana, Ek lamha nikaal kar, humein bhi yaad dilaana. Zindagi ke is rangmanch par, humara bhi kirdar tha, Tumhare muskuraahat ka, ek hissa bhi hamara tha. Kabhi raat ki tanhaayi mein, sitaaro

❤‍🔥4😢4👍3💔3🕊31🥰1

Signed Aᴠɪ〄

3 Nov 2023, 12:41 UTC≈11,600 views280 reactionsread 11 August 2026

Account delete Kiya tha mra nahin tha 🥺😅

👎118😱43🤬30😢25🥰2411👏8🤩8

Signed Aᴠɪ 〄

2 Nov 2022, 15:48 UTC≈12,000 views40 reactionsread 11 August 2026
Sticker

Sticker, posted without a caption

😢23😁7👍4💋2😍2🏆1💔1

Signed Aᴠɪ 〄

31 Oct 2022, 15:52 UTC≈11,700 views38 reactionsread 11 August 2026
File

It is with a heavy heart that I bid farewell to each and every one of you who have supported me on this journey. Your unwavering support has been a constant source of inspiration and strength, and I am grateful beyond words. But now, I find myself at a crossroads. My career and personal life demand more of my time and energy, and I must focus on the path ahead. As I take this step forward, I carry with me the love yo

😢22👍5👏4🥰32🔥2

Signed Aᴠɪ 〄

31 Oct 2022, 15:32 UTC≈8,950 views256 reactionsread 11 August 2026

ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ r e a c t

🥰7163🤩44🔥33👍30👏15

Signed Aᴠɪ 〄

31 Oct 2022, 12:56 UTC≈9,680 views569 reactionsread 11 August 2026
Photo

🌸💖😑 @iavishukla » @busyAvi ❤️

👍335🔥21016🥰5❤‍🔥1🌚1🐳1

Signed Aᴠɪ 〄

31 Oct 2022, 12:55 UTC≈8,020 views25 reactionsread 11 August 2026

Before And Now😂 Kha lo Guys ❤️ @iavishukla » @busyAvi

🥰21😁4

Signed Aᴠɪ 〄

28 Oct 2022, 16:15 UTC≈6,440 views30 reactionsread 11 August 2026
File

tum mere ho 🫂........ Full song soon🙈🫠 Join @busyAvi for more Comment💬 next song 🥰

21🤮3🤩2😢2❤‍🔥1👍1

28 Oct 2022, 14:31 UTC≈8,390 views20 reactionsread 11 August 2026

⁣Are u music 🎶 addicted 😍 Join @busyAvi Song on the voice of @iavishukla Join @busyAvi @iavishukla » @busyAvi

🥰16👍2👏2

28 Oct 2022, 01:26 UTC≈4,930 views19 reactionsread 11 August 2026

Join this channel something grand 😊😉 soon

🤯17🤔2

Signed ✨Aᴠɪ ⍣✨〄

12 Oct 2022, 04:37 UTC≈5,040 views21 reactionsread 11 August 2026

⁣'⁣You can forgive some people without welcoming them back into your life.' 'Apology, accepted , access denied.✋ 🖤🖤🖤' @iavishukla » @busyAvi

🤯21

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

Citation-graph rank

Citation-graph rank — 734,925 of 1,480,944entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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 2 registered channels — 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.

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

“अच्छा बच्चा Avi Shukla” (@busyAvi), 33 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/busyAvi.

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.