First 69, then 183: the evening my training became a boomerang

The plan – and why it sounded sensible

A meal was coming up that evening, and I knew it carried carbohydrates: beef strips with sweet potato, a tomato tortilla and a protein yoghurt. My established way of handling that is movement. So at about 19:57 I got on the bike for 30 minutes of low impact riding plus a five-minute cool-down.

I knew the pattern from earlier the same day. I had already ridden at midday, and it had worked – at least in the sense in which I understood „worked“ back then.

The morning as a contrast

At about 11:57 a 30-minute ride began. My value was around 143 mg/dl at the time, having climbed slowly through the morning. After the training, at 12:32, it stood at 87 mg/dl – with a falling arrow. A drop of roughly 56 points.

Screenshot of the Libre app showing 87 mg/dl at 12:32 after the Peloton ride — Fig. 1: After the morning ride – 87 mg/dl and still falling. The app interface is in German.

At the time I thought: that went well. By 13:21 I was back at 118, and the afternoon passed quietly between 105 and 125. In hindsight that was already the first hint I read past – training that pushes the value down by more than 50 points is not working against a meal. It is working against my reserves.

The evening: 69 mg/dl

At 20:18, a good 20 minutes into the second session, the app reported low glucose. 69 mg/dl, arrow still pointing down. I had trained before there was anything to metabolise – and the muscle took what it needed from the blood.

Screenshot of the Libre app showing the low glucose warning at 69 mg/dl at 20:18 — Fig. 2: 20:18 – the alarm. 69 mg/dl with a falling arrow, in the middle of the training session.

Three minutes later I ate and logged it in the app. Not as a countermeasure against the low value, but because the meal was due anyway. That very simultaneity became the problem.

Screenshot of the Libre app with the meal note at 20:21 — Fig. 3: The meal at 20:21 – protein yoghurt, beef strips with sweet potato, tomato tortilla.

And then: 183

At 21:02 the display read 183 mg/dl, arrow climbing steeply. In a good 40 minutes my value had risen by 114 points. That is more than the meal alone explains – sweet potato and a 50-gram tortilla are hardly a sugar bomb.

Screenshot of the Libre app showing 183 mg/dl with a rising arrow at 21:02 — Fig. 4: 21:02 – 183 mg/dl. The curve shows the trough and the steep climb right after it.

Fig. 5: The whole day at a glance. Two training windows, one low, one high.

What actually happened

Two sources of glucose arrived at the same time. One came from outside, the other from within me.

Fig. 6: Four steps that together explain the swing.

The liver steps in. When blood sugar falls towards 70, that is a signal for the body. Glucagon rises and the liver releases stored glucose. This is not a defect but a protective mechanism – it stops the value dropping further.¹ It simply keeps running when supplies from outside are already on their way.

Fat delays the meal. Beef strips and tortilla bring fat with them, and fat slows gastric emptying. The carbohydrates from the sweet potato therefore did not arrive at once but with a lag.² Precisely at the moment when the liver was already delivering.

🔍 Why the training did not catch the rise

Movement lowers blood sugar reliably – but only while it lasts, and only while there is something to burn.³ My ride was over at 20:32. The rise began after that. I had placed the movement where there was nothing yet, and it was missing where the peak arrived.

The walk afterwards

At 21:04 I set off. Nine minutes, 799 metres, average heart rate 121 – no athletic feat, more a stroll around the block in Bad Neuenahr-Ahrweiler.

Screenshot of the workout details: outdoor walk, 8:47 minutes, 799 metres, 121 bpm — Fig. 7: The walk at 21:04 – short, easy, placed directly into the rise.

My impression that evening was that this short walk did more than the half hour on the bike before it. That sounds contradictory, but it is plausible: the walk sat inside the rise, the ride sat before it. In matters of timing, placement beats intensity.

How it ended

The peak did not last. By 21:30 I was at around 128, by 21:45 at about 108 – back in the target range, a good 45 minutes after the high point. The night then stayed calm: a flat wave between 110 and 126, with no second swing. At 00:29 the display read 104 mg/dl with a level arrow.

Screenshot of the Libre app at 00:29: 104 mg/dl in the target range, with the course of the evening — Fig. 8: 00:29 – 104 mg/dl. Looking back you can see the trough, the peak and the quiet night that followed.

That answers the earlier question, at least for this one evening: the swing stayed an episode. No after-burn, no second rise around midnight, no rebound low. Whether the walk caused that, or whether the curve would have turned anyway, cannot be separated from a single case – that would need the same evening without the walk. What is certain: the fall began immediately afterwards.

🔎 A side finding about the app itself

In the 12-hour window the curve shows a high of about 160 mg/dl and a low of around 86 – yet what I measured was 183 and 69. The wider the time window, the more the display smooths the peaks away. Anyone looking only at the daily curve underestimates both extremes. The spot readings are the more reliable basis.

What I take from it

The mistake was not the movement. It was assuming that movement before a meal does the same job as movement during the rise. With a fatty meal the peak shifts backwards – and my buffer was long behind me by the time it was needed.

There is a second point I had never seen this clearly before: a low value is not merely a low value. It provokes a counter-movement that helps drive the later rise. Anyone who works their way below 70 is then fighting on two fronts.

⚠️ Important for anyone on medication

I take no glucose-lowering drugs – for me 69 mg/dl was unpleasant but manageable. On insulin or sulfonylureas the same number looks different: there, training on empty stores can lead to a genuine hypo. Anyone taking such medication should settle training times and meal intervals with their doctor rather than choosing them from a blog article.

How I will try it next time

Not riding before the meal but after it – and later than feels right. With a fatty meal, rather 45 to 60 minutes of distance than straight afterwards. Shorter and easier instead of 30 minutes in one block.

The evening ended on a conciliatory note, and that is exactly what makes it instructive: a value of 183 is no disaster if it stays an episode. More interesting than the peak is how quickly it resolves. What is still missing is the counter-test – the same meal, the same timing, but without the walk around the block. Only that would show how much of it really was the movement.

Key takeaways

Two rides on the same day: 143 to 87 mg/dl at midday, down to 69 mg/dl in the evening.
At 20:18 a low glucose alarm – the training came before the meal, not after it.
After eating at 20:21 the value climbed to 183 mg/dl by 21:02: +114 in a good 40 minutes.
Two sources coincided: liver glucose from counter-regulation, and the delayed carbohydrates of a fatty meal.
The training ended at 20:32 – that is, before the rise had even begun.
A nine-minute walk at 21:04, by contrast, sat right inside the rise.
By 21:45 the value was back in range and the night stayed calm – 104 mg/dl at 00:29.
The 12-hour view smooths the peaks: it shows 160 and 86, whereas the measurements were 183 and 69.

Article-specific in-depth assessment

The original measurement record remains unchanged. This section adds only method, sources, limitations and a reproducible follow-up plan.

The central question in this article

The article “First 69, then 183: the evening my training became a boomerang” examines why a low of 69 and a later value of 183 require a complete timeline and safety context. The quality test is not whether one curve creates a compelling story. It is whether the timeline, data source, surrounding circumstances and alternative explanations are documented well enough for readers to separate observation from interpretation.

Article-specific context for First 69, then 183: the evening my training became a boomerang — Direct observation, plausible explanation and open question remain separate.

What the data show — and what they do not

A personal series can show timing and recurring patterns. It cannot by itself prove which physiological mechanism caused the pattern. Direct observation, plausible explanation and open question are therefore separated. Numbers remain linked to unit, time and data source, and missing details are not replaced with guesses.

Reading CGM correctly

Continuous glucose monitoring measures interstitial glucose. During rapid rises or falls, the display may follow blood glucose with a delay. Pressure on the sensor, a newly inserted sensor, hydration and short data gaps can add uncertainty. When a reading does not match symptoms or the situation, a confirmatory measurement may be appropriate depending on the clinical significance.

Technical context: Movement and exercise

Activity can increase glucose uptake by working muscle. At the same time, intense exercise can increase endogenous glucose supply through stress hormones. The direction of the curve therefore cannot be predicted from the word “exercise” alone. Duration, intensity, training status, starting value and the previous meal all matter. For comparisons, intensity should not be described only by a class name or a subjective label. Duration, heart rate, power, pauses, perceived exertion and time of day are more informative. When these data are missing, the interpretation must remain cautious.

Timeline for First 69, then 183: the evening my training became a boomerang — The four phases prevent isolated readings from being detached from their timeline.

Article-specific interpretation

For “First 69, then 183: the evening my training became a boomerang”, this means first establishing which of the four phases — Starting value and trend, Start and intensity, Immediate response, Follow-up to 3 hours — are actually documented. A missing phase is not guessed from the curve. This matters especially because why a low of 69 and a later value of 183 require a complete timeline and safety context. More decimal places do not improve research; more complete context does.

Alternative explanations

The competing influences considered are Exercise intensity, Meal and timing, Liver glucose and stress, Medication and hypo risk. Several can act at once and partly mask one another. No factor is therefore declared causal merely because it occurred close in time. A plausible explanation remains labelled as plausible until a targeted comparison supports it.

Data sheet and provenance

The data sheet for “First 69, then 183: the evening my training became a boomerang” records more than the start and peak. It also covers Starting value and trend, Start and intensity, Immediate response and Follow-up to 3 hours. Each section states whether a value was measured directly, read from a screenshot, calculated from raw data or reconstructed from memory. This keeps strong research separate from details that require later verification.

Typical failure modes

Common failure modes in this topic are incomplete portions, an incorrect time origin, events added retrospectively and observation ending too soon. For “First 69, then 183: the evening my training became a boomerang”, Exercise intensity and Liver glucose and stress are particularly important competing explanations. A finding is therefore given more weight only when the same direction appears on several sufficiently similar days and counterexamples are documented as well.

Editorial decision

The editorial decision is to keep the personal experience visible without turning it into universal advice. Headline, hero image, alternative text, captions and conclusion must communicate the same uncertainty. When the article contains an open question, it ends with the next testable step — Record the starting value — rather than a claim of effect.

Interpretation matrix

The interpretation matrix for “First 69, then 183: the evening my training became a boomerang” assigns every core statement to one of four classes: directly measured, calculated from several readings, physiologically plausible or still open. Direct measurement does not automatically establish causation. A calculated result requires a documented formula and time window. Plausible means consistent with physiology and timing but not isolated in the personal data. Open means that data, repetitions or comparison conditions are missing.

Publication review

Before publication, a final review asks whether the hero image matches the actual message of “First 69, then 183: the evening my training became a boomerang”, whether every number can be found in the text, whether units and timing are correct, and whether every image has alternative text and a caption. It also checks that Exercise intensity or Meal and timing has not accidentally been turned into a proven cause. Only then is the article editorially complete.

Influencing factors for First 69, then 183: the evening my training became a boomerang — Several factors may act at once; the graphic organises them but proves no cause.

Reproducible follow-up plan

The next useful comparison follows four steps: Record the starting value, Log heart rate/power or effort, Observe during and after, Assess the next day separately. This sequence turns a spontaneous observation into a protocol and reduces the risk of selecting only spectacular days while forgetting ordinary patterns.

What can be transferred

The transferable lesson from “First 69, then 183: the evening my training became a boomerang” is therefore not necessarily the exact number. What transfers are the question, the documented conditions and the handling of uncertainty. Other people may respond very differently because of treatment, fitness, insulin sensitivity, digestion or comorbidity.

Comparison rather than snapshot

A credible comparison starts with one clear question and conditions that are as similar as possible. Starting value, trend, time, portion, drinks, activity, sleep, stress and medication all belong in the record. Not every factor can be controlled; the important point is to show differences rather than explain them away afterwards.

State the observation window

Thirty minutes answers a different question from two, four or twelve hours. The article therefore states when observation begins and recognises that mixed meals, alcohol or intense activity can act later. A peak is not interpreted without the pattern before and after it.

Personal readings are not universal limits

Typical guideline targets can provide orientation but require individualisation. Age, comorbidities, pregnancy, medication, hypoglycaemia risk and personal treatment goals change the interpretation. The self-observations shown here do not replace diagnosis or treatment decisions.

Practical safety framework

Marked symptoms, recurrent hypoglycaemia, very high readings, ketones or a pattern that does not fit the situation require clinical assessment rather than another self-experiment. People using insulin or glucose-lowering medication must not derive dose changes or corrections from a blog post.

Further technical limitations

A fall during a session and a later rise can both be plausible. Muscle uptake, digestion, stress responses and liver glucose output do not necessarily peak at the same minute. A complete timeline matters more than the lowest or highest isolated reading. For people using insulin or sulfonylureas, exercise may contribute to hypoglycaemia during activity or several hours later. Medication adjustments require individual clinical guidance. With very high glucose, ketones or marked illness, exercise is not a safe correction strategy.

Follow-up protocol for First 69, then 183: the evening my training became a boomerang — The follow-up changes only a few factors and records deviations before analysis.

Questions before drawing a conclusion

Is the starting value for “First 69, then 183: the evening my training became a boomerang” documented with trend and time?
Are Exercise intensity and Meal and timing described adequately?
Did observation continue through “Follow-up to 3 hours”?
Is there a comparison day after “Record the starting value”?
Is each statement clearly labelled as personal, plausible or generally established?

Sources and context

Medical notice: This article explains a personal observation and general context. It does not replace diagnosis, treatment adjustment or emergency care.

Sources

Sources as of: 25 Jul 2026.

Counter-regulation as blood sugar falls: glucagon and adrenaline trigger glucose release from the liver; the mechanism starts within the lower normal range. Review. ncbi.nlm.nih.gov/PMC5375488 (opens in a new window)
Fat slows gastric emptying and shifts the glucose peak later; mixed meals therefore act later and flatter, but for longer. Diabetes Care. care.diabetesjournals.org (opens in a new window)
Physical activity, GLUT-4 and insulin sensitivity: insulin-independent glucose uptake in muscle; acute during and shortly after a session. PMC (2020). pmc.ncbi.nlm.nih.gov/PMC7235686 (opens in a new window)

One case within a broader pattern

The new case-series review identified twelve sessions with an initial fall and a later rebound. That makes the sequence less isolated but still does not prove one cause. The new article “Hard Peloton rides and the glucose bounce” sets out the selection rule, numbers and limits.