Channel
@FractalProjects
On this record: Topic ยท Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Citations ยท Cite this entry
36,646subscribers
+488 since we began measuring on 6 August 2026
Risers and fallers across the register ยท movement among entries of 31,623โ100,000.
| Telegram ID | -1002177276009 |
|---|---|
| Type | Channel |
| Username | @FractalProjects |
| Created | 5 June 2024 โ measured โ dated from the channelโs first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/FractalProjects |
Technology โ 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 69% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 14:36 | 36,646 | -8 |
| 9 Nov 2026, 00:56 | 36,654 | -6 |
| 7 Nov 2026, 14:56 | 36,660 | +5 |
| 6 Nov 2026, 15:48 | 36,655 | -8 |
| 5 Nov 2026, 13:58 | 36,663 | -7 |
| 4 Nov 2026, 15:26 | 36,670 | -12 |
| 3 Nov 2026, 13:37 | 36,682 | -19 |
| 2 Nov 2026, 12:58 | 36,701 | +7 |
| 1 Nov 2026, 16:16 | 36,694 | +6 |
| 31 Oct 2026, 14:17 | 36,688 | -12 |
| 30 Oct 2026, 17:26 | 36,700 | +8 |
| 29 Oct 2026, 19:39 | 36,692 | -20 |
| 28 Oct 2026, 21:47 | 36,712 | +9 |
| 27 Oct 2026, 23:59 | 36,703 | +8 |
| 26 Oct 2026, 23:30 | 36,695 | +7 |
| 26 Oct 2026, 02:17 | 36,688 | +3 |
| 25 Oct 2026, 02:44 | 36,685 | +17 |
| 24 Oct 2026, 00:31 | 36,668 | +11 |
| 23 Oct 2026, 01:08 | 36,657 | -2 |
| 22 Oct 2026, 02:50 | 36,659 | first reading |
5 posts held, back to 5 June 2024 โ the reader has reached the start of this channelโs public history, so this is the full archive Telegram still exposes. Read across 179 pages 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 5 posts for this entry, the most recent from 9 July 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegramโs own channel header, read 11 November 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.
4,877 reactions across 4 posts, in 17 distinct kinds. The most used accounts for 34.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ๐ | 1,659 | 34.0% | |
| โค | 1,380 | 28.3% | |
| ๐ฉ | 360 | 7.38% | |
| ๐ฅ | 284 | 5.82% | |
| ๐ฅฐ | 278 | 5.70% | |
| ๐ | 227 | 4.65% | |
| ๐ | 222 | 4.55% | |
| ๐ | 77 | 1.58% | |
| ๐คฎ | 69 | 1.41% | |
| ๐ฅฑ | 61 | 1.25% | |
| ๐ | 59 | 1.21% | |
| ๐คทโโ | 59 | 1.21% | |
| ๐ | 55 | 1.13% | |
| ๐ | 37 | 0.759% | |
| ๐ป | 33 | 0.677% | |
| ๐ | 13 | 0.267% | |
| ๐คก | 4 | 0.082% |
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 4 of the 5 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 4,877 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 5 most recent posts we hold, published 5 June 2024 to 9 July 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Filmigobot V2 Features: โข About, Help & Privacy Commands โข Command Callbacks โข Imdb Command โข Justwatch Command โข Open Callback Handler โข Style & Performance Fixes View the Demo Bot @SurfOTTBot or deploy to vercel now ๐ฅ
๐893โค773๐ฉ161๐ฅ119๐ฅฐ83๐74๐70๐ฅฑ61
๐ฅ Introducing @SurfOTTBot a fully Serverless and Opensource bot to check the OTT availability of a movie or get it's IMDb data. You can connect your own bot to the public app Here.
๐402โค289๐ฉ120๐88๐ฅ88๐ฅฐ57๐41๐40
.
โค126๐117๐คฎ69๐68๐ฅฐ67๐32๐ฅ27๐คก2
๐๐ผ Welcome to @FractalProjects We build simple efficient telegram bots with User Experience as the key priority. Our projects focus mostly on serverless platforms to leverage the powers of infinite scaling and zero downtimes. Join us on this journey as we test the full capabilities of telegram's APIs and it's limits.
๐247โค192๐ฉ79๐75๐ฅฐ71๐ฅ50๐ 37๐37
Channel created
Showing the 5 most recent of 5 posts we hold for @FractalProjects. 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.
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.
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.
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 10 November 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐ฟ๐ฎ๐ฐ๐๐ฎ๐นโ (@FractalProjects), 36,646 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/FractalProjects.
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.