Channel
@PostoDocs
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
864subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002488463712 |
|---|---|
| Type | Channel |
| Username | @PostoDocs |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/PostoDocs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 03:20 | 864 | no change |
| 8 Aug 2026, 03:19 | 864 | first reading |
20 posts held, back to 4 July 2025 — 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 19 July 2026 |
|---|---|
| Posts held | 20 (4 July 2025 – 19 July 2026) |
| Views total | 186 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 03:20 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 8 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.
328 reactions across 16 posts, in 10 distinct kinds. The most used accounts for 55.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 183 | 55.8% | |
| 👍 | 56 | 17.1% | |
| 👏 | 30 | 9.15% | |
| 🥰 | 21 | 6.40% | |
| 🔥 | 14 | 4.27% | |
| 🆒 | 10 | 3.05% | |
| 🐳 | 7 | 2.13% | |
| ⚡ | 3 | 0.915% | |
| 🤔 | 3 | 0.915% | |
| 😎 | 1 | 0.305% |
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 18 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 328reactions 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 4 July 2025 to 19 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
📚 The knowledge base just got better You can now find guides directly in the Mini App. ✔️ Type your question into the search bar to see the most relevant guides ✔️ Tap Ask AI to get an instant answer
❤4
Sections: How to Work Safely with a Team When you have multiple channels and a team of editors, a problem arises: how do you grant access to employees while maintaining control over all channels? Usually, channel owners add editors directly to the Telegram admin panel. But this is risky — if one of the admins violates the rules, all channels they were connected to may face blocking. Sections solve this problem. Yo…
❤94👍43👏20🥰18
How to Add New Team Members Make sure the user has activated @posto. If not, they need to follow the link t.me/PostoRobot and click "Start". The username above is for the premium Posto bot. If you have your own scheduling bot, the new team member must activate it, not the premium bot. 1. In the bot, open the "Settings" menu → "Editors" and click "New Editor." 2. In the bottom menu, click "Select Users" — a contact…
❤31🔥6👏3🤔3👍1🥰1
How to Create a Separate Project and Start Working in It Projects are completely isolated workspaces. Each project has its own channels, editors, settings, and content calendar. This helps separate work — for example, keeping your channels separate from partner ones or managing multiple channel networks independently. 💡 Your first project is created automatically upon registration with a random name. You can rename…
❤20🆒10🔥3👍1
How to Post to Forum Topics Posting to topics works the same as posting to channels. You can: 🫙Set default settings for each topic 🫙Copy one post to multiple topics with different formatting 🫙Configure individual schedules for each topic 🫙Edit posts across all topics with one click Creating a Post 1. Click "Create post" in the bottom menu or send /newpost 2. Select the topic you need from the list. 3. Send your p…
👍6❤3
How to Connect a Topic to the Bot Topics are separate threads within a Telegram group that help structure communication across different areas. 💡 If the ability to create topics isn't enabled yet, go to your group settings and turn on the "Topics" toggle. 1. Connect the group to the bot using the /addchannel command 2. Then go to the topic you want to add to the bot and send the /addtopic command there You'll se…
❤8
Connecting a Group to the Bot There are two ways to connect a group — through the bot and through the administrators section in the group itself. We recommend the first method as it's very simple. First method — through the bot 1. Go to "Settings" → "New Channel/Group" or send the command /addchannel 2. Click "Select Group." 3. Choose the needed group from the list or use the search. 💡 You can only add groups whe…
❤9
How to Clear Content Plan with One Click If you need to quickly delete all scheduled posts and start with a clean slate: 1. Click "Content Plan" in the bottom menu or send /plan 2. Go to "Bulk Operations." 3. Click "Clear Content Plan" and confirm the operation. Now the content plan is empty and ready for a new phase of work. Important! If an important post was deleted while clearing the content plan, it can be r…
How to Delete All Scheduled Posts in a Channel If you decided to create a content plan from scratch, instead of deleting each post separately, it's easier to cancel all scheduled posts at once. To do this: 1. Open "Content Plan" and select the channel you need from the list. 2. Click "More" → "Bulk Operations." 3. Click "Clear Content Plan" and confirm the action. Partial Content Plan Clearing If you don't need …
How to Bulk Delete Posts from a Category If posts were scheduled on a separate schedule and you decide to delete them, this can be done in a few clicks: 1. Click "Content Plan" in the bottom menu or send /plan 2. Go to "Bulk Operations." 💡 To clear posts from a specific channel, select it first, then go to bulk operations. 3. Click "Clear Content Plan" → "Filter." 4. Select the category you need from the list and…
👏5❤2
How to Cancel a Post Scheduled to Multiple Channels This function deletes the post from all channels where it was scheduled. The following will be deleted: 🫙All post variations, including those with replaced auto-signatures or rewritten text 🫙All auto-repeats To delete a post across all channels at once: 1. Open the post in any channel through "Content plan" or "Change post" section. 2. Tap "Delete". 3. Select th…
⚡3❤1
How to Shift Publication Time for Posts Across All Channels Imagine: you scheduled posts a month ahead, then realized you used the wrong timezone. Manually correcting each post? That's like resetting the hands on a hundred clocks one by one. There's an easy solution: 1. Click "Content Plan" in the bottom menu or send /plan 2. Click "Bulk Operations" → "Shift Publication Time." 3. Send the time offset in this forma…
🐳7❤3
Showing the 12 most recent of 20 posts we hold for @PostoDocs. 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 — 637,473 of 1,169,250entries 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.
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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Posto — manual” (@PostoDocs), 864 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/PostoDocs.
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.