7 Sept 2021, 09:27 UTC≈8,320 viewsread 6 August 2026
Bot should be working now. Apologies for the inconvenience.
Channel
Group Attendance Updates
@GroupAttendanceUpdates
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
900subscribers
-20 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001161591912 |
|---|---|
| Type | Channel |
| Username | @GroupAttendanceUpdates |
| Created | 16 July 2020 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/GroupAttendanceUpdates |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 03:17 | 900 | -7 |
| 2 Sept 2026, 01:04 | 907 | -7 |
| 26 Aug 2026, 17:15 | 914 | +2 |
| 20 Aug 2026, 12:35 | 912 | -3 |
| 13 Aug 2026, 12:27 | 915 | -5 |
| 7 Aug 2026, 00:14 | 920 | no change |
| 6 Aug 2026, 17:46 | 920 | first reading |
Engagement
8 posts held, back to 16 July 2020 — 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 8 posts for this entry, the most recent from 7 September 2021. An engagement rate over an empty window would be a number about nothing.
Recent posts
7 Sept 2021, 04:07 UTC≈8,110 viewsread 6 August 2026
Hello everyone, The bot is currently down. We are currently working on migrating the bot to a new server. Thank you for your patience.
19 Jul 2021, 15:33 UTC≈10,400 viewsread 6 August 2026
With the increasing popularity of the bot, lots of people were asking technical queries in the comment section. We are trying our best to resolve your queries. To make sure that all your queries get resolved, we have opened up a support group. If you are having any technical queries or feature requests regarding @GroupAttendanceBot, just join the support group, post your queries and we will try to resolve them. http…
3 Dec 2020, 19:16 UTC≈12,700 viewsread 6 August 2026
@GroupAttendanceBot v1.1 is here Change log - Minor bug fixes - Added support for more languages - Marathi, Telugu, Indonesian - Added contribution guidelines - Added contributors list Credits @jayjkr - Marathi @theevilsyn - Telugu @Tien2 - Indonesian 📢 @GroupAttendanceUpdates ⚒ Source Code #Telegram #Bot #Group #Attendance
20 Nov 2020, 17:09 UTC≈10,100 viewsread 6 August 2026
File
File, posted without a caption
20 Nov 2020, 17:06 UTC≈9,670 viewsread 6 August 2026
@GroupAttendanceBot v1.0 is here! We've always wanted to make your lives easier. We get that the struggle of managing attendance is real, but we also know that the power of technology is unmatched. So we created our own Attendance Bot for Telegram to cut down on time and effort you spend on attendance. The beta released which was launched 4 months back, had received tremendous support and appreciation from different…
16 Jul 2020, 09:33 UTC≈7,580 viewsread 6 August 2026
🤖 @GroupAttendanceBot Keralagram is proud to announce @GroupAttendanceBot that will help teachers for their online classes. The bot will help to take attendance. Organizers can start the attendance and members can mark their attendance. Once the organizer closes the attendance, the result will be sent to admin as a CSV file which can be opened in Spreadsheet or Excel. 📢 Subscribe to @GroupAttendanceUpdates for bot …
16 Jul 2020, 08:29 UTCviews —
Channel created
Showing the 8 most recent of 8 posts we hold for @GroupAttendanceUpdates. 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.
Mentions
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.
“Group Attendance Updates” (@GroupAttendanceUpdates), 900 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/GroupAttendanceUpdates.
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.