Channel
@Flexbooru
On this record: Growth · Engagement · Posts · Citations · Cite this entry
724subscribers
-5 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001424540888 |
|---|---|
| Type | Channel |
| Username | @Flexbooru |
| Created | 29 January 2019 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/Flexbooru |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 21:02 | 724 | -5 |
| 6 Aug 2026, 16:13 | 729 | no change |
| 6 Aug 2026, 08:00 | 729 | first reading |
20 posts held, back to 3 June 2024 — 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.
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 2 February 2026. An engagement rate over an empty window would be a number about nothing.
⚠️ Important: Rule34 Login Workaround If you are experiencing issues logging into Rule34, please follow these steps to resolve the connection error: The Fix * Change the API Domain: Temporarily change api.rule34.xxx to rule34.xxx in your settings. * Log In: Perform the login process as usual. * Optional Revert: Once logged in, you can switch the domain back to api.rule34.xxx, or leave it as rule34.xxx. > Note: I…
The booru list has been updated.
[Guide] How to Retrieve Your API Key and User ID for Gelbooru [教程]如何获取 Gelbooru 的 API Key 和 User ID English: https://onlymash.github.io/BooruHubDocs/gelbooru 中文： https://onlymash.github.io/BooruHubDocs/gelbooru_chs
desktop
rule34 now returns a 404 sample url, so you need to set the details size to full to load details image
Version 1.2.0 * Added support for e621ng engine e621ng: https://github.com/e621ng/e621ng
Version 1.1.9 * Consolidate Gelbooru Legacy into Gelbooru. Note: Gelbooru 0.2 requires setting apikey and userid, which can be obtained by logging into your account on the relevant website. rule34.xxx has been upgraded to gelbooru 0.2
The new version has been submitted and is awaiting review by Google Play. You need to set your own API key and User ID for Gelbooru
gelbooru now requires an api key, waiting for the next version update to support
realbooru disabled its API
https://www.youtube.com/live/l3yDd3CmA_Y
Should BooruHub migrate to M3 Expressive? anonymous poll Migrate when it's ready🦖 – 34 👍👍👍👍👍👍👍 83% Stay on M3😁 – 7 👍 17% 👥 41 people voted so far.
Showing the 12 most recent of 20 posts we hold for @Flexbooru. 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 — 818,614 of 1,345,403entries 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“BooruHub” (@Flexbooru), 724 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Flexbooru.
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.