Telegram RegisterThe public register of Telegram

Channel

BSG MGC Public Release Channel

@Channel_MGC_BSG

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

43,780subscribers

-121 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001277963150
TypeChannel
Username@Channel_MGC_BSG
DescriptionOfficial Public BSG Google Camera Port Release Channel. —————————————————— Official Group - @PublicGroup_MGC_BSG Photography Group - @pocophoto | @WonPicKorea Config Channel - @Config_MGC ——————————————————
CreatedBetween 1 April 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/Channel_MGC_BSG

Growth

43,78043,90143,840.57 August 2026 — 43,901 subscribers7 August 2026 — 43,901 subscribers8 August 2026 — 43,896 subscribers9 August 2026 — 43,863 subscribers10 August 2026 — 43,839 subscribers11 August 2026 — 43,832 subscribers12 August 2026 — 43,810 subscribers13 August 2026 — 43,791 subscribers14 August 2026 — 43,780 subscribers7 August 202614 August 2026
9 measurements spanning 7 days, net -121. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 43,762–43,919 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 08:5743,780-11
13 Aug 2026, 02:0743,791-19
12 Aug 2026, 05:4243,810-22
11 Aug 2026, 07:1143,832-7
10 Aug 2026, 09:2143,839-24
9 Aug 2026, 06:0043,863-33
8 Aug 2026, 05:1443,896-5
7 Aug 2026, 15:3043,901no change
7 Aug 2026, 15:2243,901first reading

Engagement

22 posts held, back to 3 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
8.95%
avg views ÷ 43,780 subscribers
Avg views / post
3,920
10 posts measured
Reaction rate
0.462%
reactions ÷ views · ER floor
Posts in window
10
of 22 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held22 (3 June 202612 August 2026)
Views total39,200
Reactions total181
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 12:31 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.

What this channel posts

Photos
41
Links
180

Lifetime counters from Telegram’s own channel header, read 14 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.

Reaction mix

447 reactions across 22 posts, in 3 distinct kinds. The most used accounts for 43.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
19343.2%
🔥13229.5%
👍12227.3%

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 22 of the 22 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 447reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 3 June 2026 to 12 August 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.

Recent posts

12 Aug 2026, 16:28 UTC≈1,290 views15 reactionsread 14 August 2026

BSG public version changelog (9.7.047 from 2026/08/05): - a "Processing conveyor" menu item has been added to the module settings ("Auto", "Unsigned 16-bit", "Float 16", "Float 32-bit"); this setting affects the speed of image processing and saving, and also indirectly influences the image quality itself. - a section "Exposure correction" has been added to the module settings (divided into Auto HDR+ and Advanced H

🔥85👍2

Signed B-S-G

8 Aug 2026, 17:30 UTC≈2,780 views21 reactionsread 14 August 2026

BSG public version changelog (9.6.080 from 2026/08/08): - a "Sharp" section has been added to the "Additional settings" of the "All modes" module. - in the module's "Advanced Settings" section (for all modes), within the "Sharp" subsection, the following options have been added: "RAW Sharpen" (this menu item combines the "RAW Sharpen A" and "RAW Sharpen B" functions), "Sharp Depth 1", "Sharp Depth 2", and "Sharp l

🔥117👍3

Signed B-S-G

5 Aug 2026, 20:18 UTC≈3,420 views16 reactionsread 14 August 2026

BSG public version changelog (9.7.047 from 2026/08/05): - in the main modification settings, in the "Video" category, the "Optical video stabilization" and "Use custom profiles" items have been added, the "Video stabilization" item has been renamed to "Electronic video stabilization". - when activating the "Use custom profiles" item in the module settings, the "Custom video profile" ("Audio Bit Rate", "Audio Chann

👍105🔥1

Signed B-S-G

5 Aug 2026, 20:11 UTC≈2,960 views13 reactionsread 14 August 2026

BSG public version changelog (9.4.103 from 2026/09/03): - the "RAW Converter and YUV HDR+" section has been added to the module settings (the developer settings items: "raw16_to_raw10_converter_enable", "raw16_to_raw10_converter_faster", "yuv_hdrplus_scale_shift" and "yuv_hdrplus_faster"). - in the module settings, in the "RAW Converter and YUV HDR+" section, the "RAW16(14)(12) Conversion" category has been added,

🔥73👍3

Signed B-S-G

1 Aug 2026, 16:57 UTC≈3,890 views22 reactionsread 14 August 2026

BSG public version changelog (9.6.080 from 2026/08/01): - the following items have been added to the general menu: "LongPress on the Gallery icon" (calling up a window with "Additional settings" (patcher) of the active module) and "LongPress on the active module icon" (calling up a window with the active module settings). - a "Portrait" section has been added to the "Additional settings" of the "All modes" module.

11🔥9👍2

Signed B-S-G

29 Jul 2026, 18:01 UTC≈4,280 views16 reactionsread 14 August 2026

BSG public version changelog (9.7.047 from 2026/07/29): - the item "SHASTA" ("Default", "On", "Off", "System factor") has been added to the module settings — expanding the dynamic range of HDR+, "highlighting" dark areas in the photo, removing green and blue "spots" from dark areas of a photo. - a "Video session ID" section has been added to the "Video" category in the module settings. - the following items have

7🔥6👍3

Signed B-S-G

25 Jul 2026, 14:03 UTC≈5,110 views19 reactionsread 14 August 2026

BSG public version changelog (9.6.080 from 2026/07/25): - in the "Advanced Settings" module (divided into "HDR+ (Off / Auto / Net)" and "Enhanced HDR+ / Night Sight"), a "Lut Noise" category has been added to the "Denoise" section. - the "Lut Noise" category has been updated with "Lut Noise A", "Lut Noise B" and "Lut Noise Fix". - the options "Skip Metadata Check", "High light Fix 1", "High light Fix 2", "Disable

🔥109

Signed B-S-G

23 Jul 2026, 06:36 UTC≈5,060 views16 reactionsread 14 August 2026

BSG public version changelog (9.7.047 from 2026/07/22): - a "Video Session Quality" section has been added to the module settings under the "Video Modes" category, containing the following items: "NOISE_REDUCTION_MODE", "EDGE_MODE", "HOT_PIXEL_MODE", "TONEMAP_MODE" (if set to "Preset Curve" — "TONEMAP_PRESET_CURVE" [SRGB, REC709]), "SHADING_MODE", "COLOR_CORRECTION_ABERRATION_MODE", "COLOR_CORRECTION_MODE", "DISTORT

🔥8👍62

Signed B-S-G

18 Jul 2026, 14:39 UTC≈5,360 views21 reactionsread 14 August 2026

BSG public version changelog (9.6.080 from 2026/07/18): - a "Video Session Quality" section has been added to the module settings under the "Video Modes" category, containing the following items: "NOISE_REDUCTION_MODE", "EDGE_MODE", "HOT_PIXEL_MODE", "TONEMAP_MODE" (if set to "Preset Curve" — "TONEMAP_PRESET_CURVE" [SRGB, REC709]), "SHADING_MODE", "COLOR_CORRECTION_ABERRATION_MODE", "COLOR_CORRECTION_MODE", "DISTOR

🔥127👍2

Signed B-S-G

15 Jul 2026, 16:04 UTC≈5,050 views22 reactionsread 14 August 2026

BSG public version changelog (9.7.047 from 2026/07/15): - a "Custom request keys" section has been added to the module settings under "Session Quality" to allow setting custom request keys for the camera session; there is no limit on the number of keys. Each "Custom request key" consists of three fields: "Name" (you can select a key name from the application's database or enter a custom one), "Type" (known keys

14👍8

Signed B-S-G

11 Jul 2026, 14:57 UTC≈5,610 views25 reactionsread 14 August 2026

BSG public version changelog (9.6.080 from 2026/07/04): - a "Custom request keys" section has been added to the module settings under "Session Quality" to allow setting custom request keys for the camera session; there is no limit on the number of keys. Each "Custom request key" consists of three fields: "Name" (you can select a key name from the application's database or enter a custom one), "Type" (known keys

11👍11🔥3

Signed B-S-G

8 Jul 2026, 16:37 UTC≈5,460 views27 reactionsread 14 August 2026

BSG public version changelog (9.7.047 from 2026/07/01): - added "Session quality" section to module settings (CaptureSession for InputConfiguration, EDGE_MODE, HOT_PIXEL_MODE, TONEMAP_MODE(if = "Preset Curve" - TONEMAP_PRESET_CURVE(SRGB, REC709)), SHADING_MODE, COLOR_CORRECTION_ABERRATION_MODE, COLOR_CORRECTION_MODE, DISTORTION_CORRECTION_MODE, CONTROL_AE_ANTIBANDING_MODE, CONTROL_CAPTURE_INTENT(if = "Still Capture

13👍10🔥4

Signed B-S-G

Showing the 12 most recent of 22 posts we hold for @Channel_MGC_BSG. 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“BSG MGC Public Release Channel” (@Channel_MGC_BSG), 43,780 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Channel_MGC_BSG.

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.