Browse · recency

Telegram channels last seen posting within the week

Newest post one to seven days old — 47,912 entries on the register.

Measured against our own visit, not against the clock. When the crawler last read these channels, their newest post was between one and seven days old — publishing, but not daily. The register records when it last read each channel’s posts, and the age above is the gap between that visit and the newest post found. Saying it any other way — “posted in the last 24 hours” — would claim knowledge of what a channel did after we stopped looking, which nothing here can support.

Posts were last read across the register between 5 August 2026 and 30 September 2026. 3,941,509 entries have gone more than two days without one, so that many rows could sit a boundary out of date. A further 179,547 entries have had no posts fetched at all; they are counted separately on the index and never as dormant, because “we have not looked” is not a finding.

Listing unavailable

We could not read the channels in this band. The database did not answer this request. That says nothing about the register’s contents — only that we were unable to look. Nothing is shown rather than a partial table, because a table missing rows looks exactly like a complete one.

Every recency band

Why there is no “posts per day” band

The register does not hold every post a channel has published — for a typical entry it holds 16, one page of the public preview. Counting “posts in the last 30 days” from that measures how deep our crawl reached, not how often the channel publishes, and banding channels by it would publish a property of the crawler as a property of the channel. Recency survives the same objection because the crawler always reads the newest page first: whatever sits unread behind it, the newest post we hold is the channel’s real newest post as at that visit. How we measure.

Other ways in

The same register, arranged by measured subscriber size or by the language a channel publishes in.