
Channel
๐๐ฅ๐๐๐จ-๐๐ถ๐ต๐ฎ๐ฟ ๐จ๐ป๐ถ๐๐ฒ๐ฟ๐๐ถ๐๐ ๐ ๐๐๐ฎ๐ณ๐ณ๐ฎ๐ฟ๐ฝ๐๐ฟ
@biharUnivercitymuzaffarpur
On this record: Growth ยท Engagement ยท Citations ยท Cite this entry
15,915subscribers
Risers and fallers across the register ยท movement among entries of 10,000โ31,623.
Register entry
| Telegram ID | -1001815733598 |
|---|---|
| Type | Channel |
| Username | @biharUnivercitymuzaffarpur |
| Description | เคฏเคน เคชเฅเค เคเคพเคคเฅเคฐเฅเค เคเคฟ เคธเคนเคพเคฏเคคเคพ เคเคฐเคจเฅ เคเฅ เคเคฆเฅเคฆเฅเคถเฅเคฏ เคธเฅ เคฌเคจเคพเคฏเคพ เคเคฏเคพ เคนเฅเคเฅค เคเคธเฅ เคชเฅเค เคชเคฐ เคธเคเฅเค เคเคพเคจเคเคพเคฐเฅ เคฆเฅ เคเคพเคคเฅ เคนเฅเคเฅค ๐๐ฐ๐ง๐๐ซ ๐๐ป @Avinashfans เคฏเฅเคจเคฟเคตเคฐเฅเคธเคฟเคเฅ เคเฅ เคเฅเค เคเคพเคฎ เคเฅ เคฒเคฟเค เค เคเคฐ เคเคช เคเคฟเคธเฅ เคเฅ เคชเฅเคธเฅ เคฆเฅเคคเฅ เคนเฅ เคคเฅ เคเคธเคเฅ เคธเคพเคฐเฅ เคเคฟเคฎเฅเคฎเฅเคตเคพเคฐเฅ เคเคช เคเฅเคฆ เคนเฅเคเคเฅเฅค เคฏเคนเคพเค เคเฅเค เคชเฅเคธเคพ เคจเคนเฅเค เคฒเคฟเคฏเคพ เคเคพเคคเคพ เคนเฅเฅค |
| Created | Between 1 October 2022 and 30 September 2023 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 27 September 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 1 |
| On Telegram | t.me/biharUnivercitymuzaffarpur |
Growth
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart โ so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 01:49 | 15,915 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured โ we do not publish a rate before we have the readings behind it.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 27 September 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐ฅ๐๐๐จ-๐๐ถ๐ต๐ฎ๐ฟ ๐จ๐ป๐ถ๐๐ฒ๐ฟ๐๐ถ๐๐ ๐ ๐๐๐ฎ๐ณ๐ณ๐ฎ๐ฟ๐ฝ๐๐ฟโ (@biharUnivercitymuzaffarpur), 15,915 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/biharUnivercitymuzaffarpur.
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.