Author: Stamina Sports

  • Angsi Forest Challenge 2026 Riggers 50

    Zar Emrydeka Putera won the Angsi Forest Challenge 2026 50km in 8:57:46, ahead of Yong Kok Lam (9:24:25) and Wong Kok Wah (9:39:31). The race was two laps of the same 25km loop. Heavy rain started around 2:30pm, and most of the top 10 ran their second Riggers Hill in it.

    The fourth edition drew more than 900 participants across the weekend, including 45 international runners from eight countries.

    Race facts

    • Event: Angsi Forest Challenge 2026, Riggers 50
    • Date: 26 September 2026, 6:05am start
    • Venue: Taman Eko Rimba Ulu Bendul, Kuala Pilah, Negeri Sembilan
    • Course: two laps over Gunung Angsi (about 810m) and Riggers Hill, about 3,000m of climbing
    • Conditions: hot and humid morning, heavy rain from about 2:30pm
    • Winner: Zar Emrydeka Putera, 8:57:46

    How does the course work?

    Each lap has two big climbs. The first goes from base camp at about 170m to the Angsi summit, just over 6km into the lap, before CP1 at 6.5km. From there the trail drops along the ridge to Bukit Putus.

    The second climb is Riggers Hill. It starts from a low point of about 120m and includes one pitch that gains close to 400m in just over a kilometre. After that the trail drops back to Bukit Putus, and the lap ends with a 4km run into base camp. Then you do it all again.

    The organiser’s own line sums it up well: “Gunung Angsi will test your legs. Riggers Hill will test your mind.”

     

    Top 10: checkpoint-by-checkpoint

    FinishRunnerCP1
    6.5km
    CP2
    10.5km
    CP3
    21km
    CP4
    25km
    CP5
    31.5km
    CP6
    35.5km
    CP7
    46km
    Finish
    50km
    1Zar Emrydeka Putera1:21:31 (#2)1:51:26 (#2)3:39:47 (#1)4:03:22 (#1)5:41:09 (#1)6:19:45 (#1)8:36:35 (#1)8:57:46 (#1)
    2Yong Kok Lam1:25:14 (#4)1:55:48 (#4)3:49:17 (#2)4:09:22 (#2)5:56:58 (#2)6:37:14 (#2)9:03:18 (#2)9:24:25 (#2)
    3Wong Kok Wah1:27:48 (#5)1:57:47 (#5)3:54:43 (#3)4:16:04 (#3)6:08:58 (#3)6:50:55 (#3)9:19:03 (#3)9:39:31 (#3)
    4Teh Kah Seong1:24:35 (#3)1:55:34 (#3)3:58:59 (#4)4:21:33 (#4)6:42:38 (#4)7:26:40 (#4)9:50:59 (#4)10:12:02 (#4)
    5Arif Hakimi Nurdin1:32:12 (#9)2:03:54 (#8)4:15:14 (#7)4:40:30 (#7)6:47:33 (#6)7:29:34 (#6)10:08:23 (#6)10:33:23 (#5)
    6Adham1:32:11 (#8)2:03:53 (#7)4:15:13 (#6)4:40:29 (#6)6:47:32 (#5)7:29:33 (#5)10:08:22 (#5)10:33:24 (#6)
    7Wan Mohamad Khalif1:31:12 (#6)2:05:59 (#9)4:28:15 (#9)4:53:42 (#9)7:02:24 (#7)7:47:13 (#7)10:37:26 (#7)10:59:05 (#7)
    8Pejal1:20:14 (#1)1:50:43 (#1)4:12:51 (#5)4:37:23 (#5)7:09:47 (#9)8:01:58 (#9)10:41:22 (#8)11:07:35 (#8)
    9Muhammad Zulhazwan1:38:20 (#10)2:12:32 (#10)4:36:50 (#10)5:01:34 (#10)7:09:38 (#8)8:01:15 (#8)10:51:12 (#9)11:15:57 (#9)
    10Muhmmad Zulhijar Djabir1:31:39 (#7)2:03:47 (#6)4:18:32 (#8)4:46:25 (#8)7:15:47 (#10)8:06:20 (#10)11:03:35 (#10)11:28:55 (#10)

     

    Pejal took it out hard

    Pejal led at the summit in 1:20:14 and was still in front at Bukit Putus (10.5km). Only five minutes covered the first five runners.

    Then came Riggers Hill. Pejal needed 2:22:08 for that section and dropped to fifth. Zar ran it in 1:48:21 and was never headed again.

    Zar won it on the second Angsi climb

    Zar reached halfway at 10:08am, six minutes clear. His second Angsi climb took 1:37:47, only 16 minutes slower than his first. By 31.5km his lead had grown to almost 16 minutes.

    He posted the fastest split in five of the eight sections. His second lap was only 21% slower than his first, the smallest drop in the top 10. He didn’t speed up. He just slowed down less than anyone else.

    What did the storm do?

    The rain started at about 2:30pm. Zar was already over Riggers Hill by then, on his way down to Bukit Putus. He reached CP7 at 2:42pm.

    By 3pm the trail was carrying water like a river, and it was getting dark under the trees. Zar was a few minutes from the finish. Every runner from second to tenth was still somewhere between Riggers Hill and Bukit Putus.

    Zar crossed the line at 3:03pm. For everyone chasing him, the second lap had become a different race.

    Teh came back from the dead

    Teh Kah Seong had a bad patch on the second Angsi climb in the late-morning heat. It took him 2:21:06, almost an hour slower than his first time up. Hakimi and Adham closed to within five minutes of him.

    Plenty of runners would have faded from there. Teh didn’t. He reached Riggers Hill as the rain arrived and ran the section in 2:24:19, the second-fastest split in the top 10 after Zar. He finished fourth in 10:12:02, 21 minutes clear of the pair behind him.

    Hakimi and Adham ran it as a team

    Arif Hakimi Nurdin and Adham crossed the start mat a few seconds apart and joined up on the first climb. From then on they were never more than one second apart at any checkpoint. On three sections their splits were identical to the second.

    Adham was one second ahead at every checkpoint. At the finish it was Hakimi who crossed first, 10:33:23 to 10:33:24, fifth and sixth. They did 50km, two climbs of Riggers Hill and one storm without splitting up once.

    The rest of the top 10 earned it too

    Wong Kok Wah (3rd) ran the most patient race at the front. He was fifth at 10.5km, third by 21km, and held that place to the end. His last 4km took 20:28 in the rain, the fastest closing split in the top 10.

    Wan Mohamad Khalif (7th) was ninth at halfway and moved up two places on lap two. His final 4km was quicker than the same stretch on lap one.

    Muhammad Zulhazwan (9th) was tenth at halfway but moved up to eighth early on lap two. After Zar, he had the smallest second-lap slowdown in the top 10, at about 24%. Pejal passed him back on the wet Riggers Hill section, but it was still one of the best-managed races in the field.

    Pejal (8th) paid for his fast start and slid to ninth. On the wet Riggers Hill section he fought back past Zulhazwan and held eighth to the finish. Leading a race like this for 10km takes nerve.

    Muhammad Zulhijar Djabir (10th) spent longer on the wet Riggers Hill and Bukit Putus stretch than anyone else in the top 10. The rain started while he was already on it, and he didn’t reach CP7 until after 5pm. He still held on for a top-10 finish.

    Final results

    #RunnerTimeLap 2 vs lap 1
    1Zar Emrydeka Putera8:57:46+21%
    2Yong Kok Lam9:24:25+26%
    3Wong Kok Wah9:39:31+26%
    4Teh Kah Seong10:12:02+34%
    5Arif Hakimi Nurdin10:33:23+26%
    6Adham10:33:24+26%
    7Wan Mohamad Khalif10:59:05+24%
    8Pejal11:07:35+41%
    9Muhammad Zulhazwan11:15:57+24%
    10Muhammad Zulhijar Djabir11:28:55+41%

    What does Angsi teach?

    The race doesn’t start until the second Angsi climb. Everyone who kept their second lap within about 25% of their first either moved up or held their place. The two runners who dropped more than 40% both slid down the order.

    If you’re racing here next year, plan to meet Riggers Hill in the afternoon rain, because you probably will.


    Katsuo Stamina Race Field Notes. We cover endurance racing in real Malaysian conditions: heat, humidity, long climbs and afternoon storms. Racing Angsi next year? Elec Stamina has 220 mg of sodium per caplet, for use during or after sustained physical activity. 

  • How Much Sodium Do You Lose Running in Malaysian Heat?

    How Much Sodium Do You Lose Running in Malaysian Heat?

    In one large sweat-testing dataset, endurance athletes lost an average of 51.7 mmol of sodium per hour. That works out to roughly 1.2 g, close to half a teaspoon of salt, soaked into your singlet before most of Kuala Lumpur has had breakfast. Stretch that over a three-hour Sunday long run and you are near 9 g of salt.

    Most runners hear that and reach for salt tablets. For many of them, that is the wrong reaction. The loss is real, but whether you need to replace it during the run comes down to two things you can actually measure.

    Where the 1.2 g comes from

    The number comes from the Gatorade Sports Science Institute, which pooled data from 1,303 athletes tested between 2000 and 2017. Endurance athletes in that group sweated about 1.28 litres an hour on average. One mmol of sodium is 23 mg, so their average hourly loss comes to about 1,190 mg.

    The average hides a big spread. The standard deviation on that sodium figure was 27.8 mmol an hour, so one standard deviation around the mean spans roughly 550 mg to 1,830 mg an hour. That is more than a threefold difference between runners who would both count as normal.

    Endurance athletes were among the biggest losers in the dataset. Only American football players lost more sodium per hour, at 55.9 mmol. Footballers, basketball and baseball players all lost less, mainly because they sweat less per hour and stop sooner.

    What Malaysian humidity changes

    Heat makes you sweat. Humidity makes that sweat less useful. Sweat cools you by evaporating, and thick, wet air slows evaporation down. Researchers at Universiti Sains Malaysia in Penang described it in a 2019 study: in humid air, sweat drips off the skin instead of evaporating, so much more of the fluid you lose does nothing to cool you.

    The same study tested nine well-trained runners who were not heat-adapted, in warm-humid and warm-dry conditions. After an hour of running, they lasted 9.1 minutes in the final all-out test in humid air, against 12.7 minutes in dry air. Drinking water during the run did not reduce their thermal strain in either condition.

    Those runners were not adapted to heat, and that matters, because adaptation works in your favour. In one lab study of eight men exercising in the heat for ten days, sweat sodium concentration fell from about 54 to 36 mmol per litre, a drop of roughly a third. The catch is that heat-adapted bodies tend to sweat more, so the total sodium lost can still be large. Training in the Klang Valley does not make you a low-sodium runner. It makes your sweat less salty, but you can still lose a lot overall.

    Losing sodium is not the same as needing to replace it

    This is where most sodium advice goes wrong. Your body holds a buffer, and blood sodium only drops in particular situations.

    Alan McCubbin, an accredited sports dietitian, modelled this directly. He tested sweat sodium from 20 to 80 mmol per litre, sweat rates from 0.5 to 2.5 litres an hour, and fluid replacement from 10% to 90% of losses. The result was blunt. For a football match and an elite marathon, replacing sodium was unnecessary in every realistic scenario. The 160 km ultramarathon was different: runners whose sweat held 40 mmol per litre or more, and who drank back over 80% of their losses, needed to replace at least 47% of their sodium.

    The model found that two things drove sodium needs: the share of your sweat loss you drink back, and how salty your sweat is. Duration multiplies both. McCubbin has also written that there is little if any evidence that sodium during exercise improves performance, at least in efforts under four hours.

    One honest gap: an elite marathon takes about two hours, while a recreational marathon in Malaysian heat can take five. The race scenarios in the model did not cover that middle ground. The same two drivers still apply, so the longer you are out and the more you drink, the more your sodium plan matters.

    The water bottle is the bigger risk

    The dangerous form of low blood sodium, exercise-associated hyponatraemia, usually is not caused by sweating out too much salt. An international consensus panel concluded that the main cause is drinking too much dilute fluid, likely combined with hormone signals that make the body hold on to water during exercise. More salt is not the fix. Less fluid is.

    The panel’s advice is to drink when thirsty. Early signs include lightheadedness, nausea and gaining weight during an event. If you finish a long run heavier than you started, you drank too much, whatever was in the bottle.

    Find your own number

    An average is only a starting point. You can measure your own sweat rate with a bathroom scale, which is essentially how the big dataset did it: change in body mass during exercise, corrected for what athletes drank and passed.

    1. Use the toilet, then weigh yourself in minimal clothing before a 60-minute run.
    2. Run at a normal training effort and note how much you drink.
    3. Towel off and weigh again in the same clothing.
    4. Add the weight you lost to the fluid you drank. That is your hourly sweat loss, with 1 kg being roughly 1 litre.

    Do it once on a hot, still morning and once after overnight rain. The gap between the two tells you how much your race-day plan should shift with the weather.

    Saltiness is harder to measure at home. White tide marks on your cap or singlet hint that your sweat is on the salty side, but they are not a measurement. If you race ultras and see those marks often, a proper sweat sodium test is worth paying for.

    When sodium belongs in your plan

    Up to about two hours, drinking to thirst: your normal meals cover your sodium. Salty food or drink is a season-to-taste choice rather than a requirement.

    From two hours to around five, such as a long run or a recreational-pace marathon at KLSCM, it depends on your numbers. If you drink back most of what you sweat and your sweat is salty, planned sodium starts to make sense. If you drink to thirst, you likely have more room than most advice suggests.

    Ultras are where the modelling says sodium genuinely matters, when long exercise is combined with drinking back more than 80% of losses and sweat sodium of at least 40 mmol per litre. Plan your intake per hour, not per aid station.

    What this looks like at KLSCM

    The KLSCM full marathon cut-off has run to 7 hours 15 minutes, so a large part of the field is out there for five hours or more. That runner is in a completely different position from the two-hour elite the model said needs nothing.

    Say you measured 1.2 litres an hour at race pace during training. Over five hours that is about 6 litres of sweat. At 920 mg of sodium per litre, the illustration figure below, the theoretical loss is around 1,100 mg an hour.

    That number is not a target to match. Your drinking rate, your food, your own sweat concentration and the length of your race all change what you actually need. What it does tell you is whether you are the kind of runner the research is talking about: long time on feet, heavy sweating, and drinking back a lot of it.

    Turning your number into a plan

    Each Elec Stamina caplet contains 220 mg of sodium. On its own that figure means nothing. Next to your own numbers it does the work for you.

    The arithmetic runs like this. Take your hourly sweat loss in litres from the scale test, multiply it by your sweat sodium in mg per litre, and you have your hourly loss. Without a sweat test you cannot know your own concentration, so use 40 mmol per litre, about 920 mg per litre, only as an illustration. That figure sits above the average, so it overstates the loss for a lot of runners. It is the level at which McCubbin’s ultramarathon scenario made targeted replacement necessary, not a diagnosis of salty sweat.

    Then decide what share you intend to replace. The ultra scenario in the model landed near half for salty sweaters drinking back most of their losses. Divide that figure by 220 and you know how many caplets an hour that is for you, and how many to carry for a race that takes eight hours rather than four.

    Whatever the maths says, stay within the directions on the pack, and rehearse the plan on long runs at race effort, in the heat you will race in.

    Running KLSCM, an ultra, or another long race in the heat?

    Measure your sweat rate on a long training run first. Once you know roughly how much fluid you lose an hour, you can build a sodium schedule around your race duration instead of guessing at an aid station.

    Elec Stamina provides 220 mg of sodium per caplet, which makes it simple to carry and to count.

    References

    1. Barnes KA, Anderson ML, Stofan JR, Dalrymple KJ, Reimel AJ, Roberts TJ, Randell RK, Ungaro CT, Baker LB (2019). Normative data for sweating rate, sweat sodium concentration, and sweat sodium loss in athletes: an update and analysis by sport. Journal of Sports Sciences, 37(20), 2356-2366.
    2. Che Muhamed AM, Yusof HA, Stannard SR, Mündel T, Thompson MW (2019). The efficacy of ingesting water on thermoregulatory responses and running performance in a warm-humid condition. Frontiers in Physiology, 10, 507.
    3. Chinevere TD, Kenefick RW, Cheuvront SN, Lukaski HC, Sawka MN (2008). Effect of heat acclimation on sweat minerals. Medicine & Science in Sports & Exercise, 40(5), 886-891.
    4. McCubbin AJ (2023). Modelling sodium requirements of athletes across a variety of exercise scenarios: identifying when to test and target, or season to taste. European Journal of Sport Science, 23(6), 992-1000.
    5. McCubbin AJ (2022). How much sodium do I need? mysportscience.com
    6. Hew-Butler T, Rosner MH, Fowkes-Godek S, et al. (2015). Statement of the 3rd International Exercise-Associated Hyponatremia Consensus Development Conference, Carlsbad, California, 2015. British Journal of Sports Medicine, 49(22), 1432-1446.
    7. Hew-Butler T, Loi V, Pani A, Rosner MH (2017). Exercise-associated hyponatremia: 2017 update. Frontiers in Medicine, 4, 21.
  • Why Runners Cramp in Malaysian Heat (and What Actually Helps)

    Last updated: 21 September 2026

    The best-supported explanation for running cramps is muscle fatigue, not a simple lack of salt. In a study of 210 Ironman triathletes, running faster than usual and having cramped before predicted cramping. Dehydration and blood sodium did not. Once a cramp starts, the usual first move is to slow down and stretch the muscle.

    What causes cramps when you run?

    Nobody has settled it, but the fatigue explanation has the stronger evidence. There are two main ideas.

    The older one says you cramp because sweat has drained your fluid and salt. It’s the idea most of us grew up with. A narrative review of exercise-associated muscle cramps describes it as resting on case series and anecdotal observation, and notes that athletes have cramped while fully hydrated and taking in enough electrolytes.

    The newer idea comes mainly from Martin Schwellnus and colleagues in Cape Town. A fatigued muscle loses the normal balance between the signals that tell it to contract and the signals that tell it to relax, and the working muscle locks up. It fits what runners report: cramps hit the muscles doing the most work, late in a hard effort, and runners who cramp almost always feel that muscle tire first. Schwellnus’s 2009 review says the salt and dehydration ideas lack a convincing mechanism and that data are accumulating for the fatigue explanation. He also says more evidence is needed.

    What did the Ironman study actually find?

    Pace and cramp history predicted cramping better than hydration or blood sodium did. In 2011 Schwellnus, Drew and Collins followed 210 Ironman triathletes and tracked who cramped. Running faster than usual and having cramped before were the predictors. Dehydration and changes in serum sodium were not.

    Read plainly, that says a late-race cramp is a pacing problem before it’s a salt problem. If you started faster than you trained for, your muscles were always going to be tired early.

    So does sodium matter at all?

    Yes, just not as a cure for cramps. Sweat sodium runs from roughly 10 to 90 mmol per litre (Baker, 2017), which is about 230 to 2,070 mg in a litre. A heavy sweater on a long, hot run loses a lot. The ACSM says sodium in drinks helps palatability and fluid retention and may help people who drink large volumes. Those are good reasons to care about sodium in long sessions. They aren’t evidence that sodium stops cramps.

    That’s how we see Elec Stamina. It’s a swallow tablet with no immediate effect. It can’t stop a cramp that has already started, and we don’t claim it prevents them. Its job is putting sodium into a long session on a schedule. Each tablet has 220 mg of sodium, and the label suggests 1 to 2 tablets every 10 km. If you cramp in the last hour of a long race, look at pace and training load before you look at salt.

    What should you do when a cramp hits?

    Slow down and stretch the cramping muscle. Reviews describe stretching as the most effective remedy for an acute cramp.

    1. Slow to a walk or stop.
    2. Stretch the muscle gently and hold. For a calf, straighten the knee and pull your toes towards your shin.
    3. Walk until the tightness eases, then restart below your earlier pace.
    4. Sip if you’re thirsty. Don’t gulp.

    If the same muscle keeps cramping, ease off for the rest of the race. Finishing slower beats not finishing.

    How do you make late-race cramps less likely?

    Start at or below the pace you’ve trained. The Ironman study points at speed above your usual, so the cheapest fix is a slower first half.

    • If you’ve cramped before, run the first half more conservatively. Previous cramps predicted the next one.
    • Do long runs at the time of day and in the heat you’ll race in. Malaysia’s big road marathons start very early. The Malaysia Marathon flagged off its full distance at 12.30 am on 30 August 2026, and the KL Standard Chartered Marathon starts at 3.30 am on 4 October. Practise running long in the dark and into the morning heat.
    • Follow a drinking and sodium plan for the other reasons above. See Running in Malaysian Heat.

    The Ironman study was observational and done in triathletes. It shows what went with cramping, not what caused it, and it may not carry over to a weekend runner doing a 10K.

    FAQ

    Do electrolyte tablets stop cramps?

    There’s no good evidence they do. The stronger studies link cramps to fatigue and pace. Electrolytes still have a job in long, hot sessions, and that job is fluid and sodium balance.

    Why do I cramp in races but not in training?

    Race effort is usually higher than training effort. In the Ironman study, running faster than usual predicted cramping.

    Can you cramp if you’re well hydrated?

    Yes. Reviews describe athletes cramping while fully hydrated and supplemented.

    When should I see a doctor about cramps?

    Cramps that keep happening outside hard exercise, or that come with other symptoms, are worth checking with a doctor.


    Related: Running in Malaysian Heat · Elec Stamina

    Written by Stamina Sports Malaysia, brand owner of Katsuo Stamina, Elec Stamina and QC Stamina, in Malaysia since 2015.

    Sources

    • Schwellnus MP. Cause of Exercise Associated Muscle Cramps (EAMC): altered neuromuscular control, dehydration or electrolyte depletion? Br J Sports Med 2009;43(6):401-408. Link
    • Schwellnus MP, Drew N, Collins M. Increased running speed and previous cramps rather than dehydration or serum sodium changes predict exercise-associated muscle cramping: a prospective cohort study in 210 Ironman triathletes. Br J Sports Med 2011;45(8):650-656. Link
    • Nelson NL, Churilla JR. A Narrative Review of Exercise-Associated Muscle Cramps: Factors that Contribute to Neuromuscular Fatigue and Management Implications. Muscle Nerve 2016;54(2):177-185. Link
    • Baker LB. Sweat Testing Methodology in the Field. Sports Science Exchange 161, 2017. Link
    • ACSM Position Stand, Exercise and Fluid Replacement, 1996. Link
    • paultan.org, Malaysia Marathon 2026 flag-off times. Link
    • KL Marathon, Race Weekend Schedule. Link
  • Running in Malaysian Heat: How Should You Hydrate?

    Last updated: 21 September 2026

    Drink to thirst on short runs and check your own numbers on long ones. Athletes sweat anywhere from 0.5 to 2 litres an hour, so no single target fits everyone. In heat, sodium matters once a session passes an hour, and overdrinking plain water carries its own risk.

    How much do you actually sweat when you run in Malaysia?

    More than most people guess, and the gap between runners is huge. Athletes in general sweat between about 0.5 and 2 litres an hour, and a few pass 3 litres (Baker, 2017). The KL Marathon’s own weather page puts Kuala Lumpur at 29 to 35°C in the day with humidity around 80%. In air that wet, sweat evaporates badly, so a lot of it drips off without cooling you. You lose the water and get less of the benefit.

    The arithmetic gets uncomfortable fast. A 70 kg runner sweating 1.5 litres an hour loses 3 litres in two hours. That is 4.3% of body mass if none of it is replaced. The ACSM’s 2007 position stand sets the line at about 2%, which is 1.4 kg for the same runner.

    Should you drink to thirst or follow a plan?

    For most recreational runners, drink to thirst first, then check yourself with a weigh-in. Expert guidance splits on this. The ACSM’s 2007 position stand says the aim is to keep weight loss under 2% and to tailor the plan to the person. The 2015 international consensus on exercise-associated hyponatraemia goes further and says to use thirst as your guide, because drinking beyond thirst has been linked to deaths in athletes, marathon runners among them.

    Our view: on easy and moderate runs, thirst is good enough. A plan starts to earn its place on long, hot, hard efforts, and only after you’ve measured your own sweat.

    How do you measure your own sweat rate?

    Weigh yourself before and after a one-hour run, and count everything you drink. The ACSM lists this as the way to estimate individual sweat rates.

    1. Weigh yourself in minimal dry clothing before the run, after using the toilet.
    2. Run 60 minutes at the effort you’d race at. Note how much you drink.
    3. Towel off and weigh again in the same clothing.
    4. Sweat loss in litres = kilograms lost + litres drunk (1 kg is about 1 litre).

    Example, for illustration only: 70.0 kg before, 68.9 kg after, 0.5 litres drunk. That is 1.1 + 0.5 = 1.6 litres an hour.

    If you lose more than about 2% of your starting weight, you drank too little for that run. If your weight goes up, you drank more than you sweated, and that is the direction to worry about.

    One test is one snapshot. Sweat rate moves with pace, humidity and heat acclimatisation (Baker, 2017), so a test in an air-conditioned gym tells you little about race morning. Repeat it in the conditions you’ll race in.

    Is plain water enough in the heat?

    For runs under an hour, yes. Past an hour you are also losing sodium, and how much varies enormously. Baker’s review puts sweat sodium at roughly 10 to 90 mmol per litre. One mmol of sodium is 23 mg, so that works out to about 230 to 2,070 mg in every litre of sweat. A runner losing 1 litre an hour at a middling 40 mmol/L gives up about 920 mg an hour.

    The ACSM’s 1996 position stand suggests 0.5 to 0.7 g of sodium per litre of fluid for exercise longer than an hour. Drink 500 ml an hour at that strength and you take in 250 to 350 mg. Against a 920 mg loss, that leaves a wide gap on a long, hot run.

    This is where a sodium tablet earns a place. Elec Stamina is a swallow tablet made in China. Each tablet has 220 mg of sodium, and the label suggests 1 to 2 tablets every 10 km, up to 10 a day. At a 6 min/km pace that is 220 to 440 mg an hour, so it covers part of the 920 mg example above, not all of it. It has no immediate effect, so treat it as a schedule item: take it with water at set points in a long session, not as a rescue when you feel bad. It doesn’t replace drinking, and it isn’t a licence to drink more.

    For a 45-minute easy run you don’t need it. Water and a normal meal are fine.

    What should you drink before a hot run?

    About 500 ml roughly two hours before, then let thirst take over. That figure is from the ACSM’s 1996 stand, which also says cool fluid (15 to 22°C) gets drunk more readily. In Malaysia a bottle in your bag won’t stay cool for long. Freeze half of it overnight and top up with water in the morning.

    How do you know you’re getting it wrong?

    Too little shows up as a weigh-in loss of more than 2%. Too much shows up as weight gain during a long run, puffy fingers, nausea and light-headedness, which are the mild symptoms listed in the 2015 hyponatraemia consensus. These overlap with heat illness. If someone is confused, vomiting or has a bad headache, stop and get medical help.

    FAQ

    How much water should I drink when running in hot weather?

    Drink to thirst on short runs. On long ones, measure your sweat rate and aim to finish within about 2% of your starting weight.

    Do I need electrolytes for a 10K?

    Usually not. Most recreational 10Ks last under an hour, and the guidance on sodium in fluids starts at exercise longer than an hour.

    Can I just drink plain water on a long run?

    You can, but it leaves the sodium gap open. Drinking more than thirst asks for is the bigger risk.

    Will drinking more stop cramps?

    Probably not. The best evidence links cramps to fatigue and pace. See Why Runners Cramp in Malaysian Heat.


    Related: Why Runners Cramp in Malaysian Heat · Elec Stamina

    Written by Stamina Sports Malaysia, brand owner of Katsuo Stamina, Elec Stamina and QC Stamina, in Malaysia since 2015.

    Sources

    • Baker LB. Sweat Testing Methodology in the Field: Challenges and Best Practices. Sports Science Exchange 161, 2017. Link
    • ACSM Position Stand, Exercise and Fluid Replacement. Med Sci Sports Exerc 2007;39(2):377-90. Link
    • ACSM Position Stand, Exercise and Fluid Replacement. Med Sci Sports Exerc 1996;28(1):i-vii. Link
    • Hew-Butler T et al. Statement of the Third International Exercise-Associated Hyponatremia Consensus Development Conference. Clin J Sport Med 2015;25(4):303-20. Link
    • KL Marathon, Weather. Link
  • Ninety-Five Minutes Faster: What Ben Dhiman Added at UTMB

    Ninety-Five Minutes Faster: What Ben Dhiman Added at UTMB

    Ben Dhiman won the 2026 UTMB in 18 hours, 16 minutes and 29 seconds — the fastest winning time ever recorded at the race and the first finish inside 19 hours. UTMB lists the 2026 course at 174 km with 9,700 m of climbing. The start was delayed two hours for storms and organisers removed the Pyramides Calcaires section, so the time should not be read like a road-race course record.

    The more useful comparison is with himself. Dhiman finished second at UTMB in 2025 in 19:51:37, on a 174.2 km course with 9,920 m of climbing. That edition was also modified by weather and also bypassed Pyramides Calcaires. The two races were not identical, but the biggest route omission was shared. Dhiman was still 1 hour 35 minutes faster in 2026.

    He was not the only one moving quickly. Baptiste Chassagne finished second in 18:47:38, Caleb Olson third in 18:48:24 just 46 seconds later, and Virgile Moriset fourth in 19:00:23. Three men broke 19 hours on the same day and a fourth missed it by 23 seconds. Something about this edition was fast, though the results alone don’t explain why.

    But the number that impresses me most is not 18:16.

    It is 31:09 — Dhiman’s winning margin. He moved to the front around La Balme, 41 km in, with Chassagne still only about 45 seconds back at the Croix du Bonhomme, then made the decisive break on the descent toward Les Chapieux and never gave the lead up.

    The advantage was not perfectly linear, and that makes the race more interesting. Chassagne reduced the gap from 28:12 at Champex-Lac to 25:53 at Trient. Dhiman then opened it again, reaching Vallorcine 30:47 clear. He did not disappear early and cruise home. He built a large lead, saw part of it come back, and extended it again late.

    There is also a recorded GPS analysis of his race, broken into 19 segments: 169.38 km, +9,843 m, 18:14:01, average cadence 152 spm. It isn’t an official measurement (the caveats, which matter, are gathered near the end of this piece), but for comparing one part of his race against another, it’s genuinely useful.

    One limit matters before anything else, because it shapes everything that follows. The trace shows how Dhiman produced his performance. The official checkpoint splits show where he separated from the field. What no public dataset gives us is equivalent terrain-by-terrain movement data for Chassagne or Olson. So when the trace says he climbed a section at 822 vertical metres an hour, we cannot say that climb won him the race. We do not have the denominator.

    One race, many different jobs

    The platform reports an average pace of 6:29/km, and that number tells us remarkably little.

    Across the 19 segments, Dhiman moved from 4:17/km on runnable ground to 11:28/km on the steepest climbing.

    The opening 8.77 km from Chamonix to Les Houches took 37:33 — 4:17/km, despite containing 234 m of climbing and 262 m of descent. Then the job changed. From Les Houches to Col de Voza he covered 5.25 km with 680 m of ascent in 37:57. Pace fell to 7:14/km, cadence from 171 to 140 steps per minute, and the segment produced a vertical gain rate of about 1,075 m/h.

    Nothing had gone wrong. The terrain required a different form of locomotion.

    A 4:20 kilometre on runnable trail and a 12-minute kilometre up a steep Alpine climb are both recorded as one kilometre. Mechanically, they are different jobs.

    The full-race gradient classification makes the point at scale:

    GradientDistanceShare
    Above 20% up15.81 km9.3%
    15–20% up11.26 km6.6%
    10–15% up14.04 km8.3%
    5–10% up17.53 km10.3%
    −5% to +5%50.94 km30.1%
    5–15% down33.17 km19.6%
    Steeper than 15% down26.63 km15.7%

    Only 30% of the recorded distance was anything close to flat. About a quarter was uphill at 10% or steeper, more than a third downhill steeper than 5%. And 4,257 m of ascent — some 43% of all the climbing in the trace — came on ground above 20%.

    Look at the numbers: climbing and steep descent accounted for most of the course. Running, in the flat sense most people picture, was the exception here, not the rule.

    The biggest climb

    The largest single ascent came from Les Chapieux to Col de la Seigne: 10.51 km, +1,065 m, 1:17:45, at 822 vertical metres an hour.

    Duration matters when comparing VAM. A vertical rate held for 20 minutes and the same rate held for 80 minutes are different performances. Dhiman gained more than a vertical kilometre on the Seigne section while averaging 822 m/h across 1:17:45.

    What makes 822 interesting is less the number itself and more how much climbing it covers, and how long he sustained it.

    The steep climbs

    Two later sections stand out for gradient rather than size.

    Courmayeur to Refuge Bertone — 5.28 km, +802 m, 51:19, 937 m/h, with around 31% of the segment classified above 20%.

    Arnouvaz to Grand Col Ferret — 4.37 km, +762 m, 50:18, 909 m/h, roughly 45% above 20%, and individual kilometres at 20.7% and 24.3%.

    On this ground, speed stops being the useful measure. What matters now is running versus power hiking.

    His cadence on Grand Col Ferret averaged 120 spm, the lowest of the 19 segments. On the descent immediately after — 9.7 km and 1,025 m down to La Fouly — it returned to 171.

    Cadence does not tell us how hard either effort was, or whether economy and force production had deteriorated underneath. But the abrupt change is useful descriptively: he had not become trapped in one slow movement pattern. The terrain changed and so did he.

    That switching is more interesting than the cadence itself. Strong mountain runners can climb quickly. Ultra performance asks the harder question — can you climb hard, descend afterwards without destroying the legs, and then run again when the trail allows it?

    By Grand Col Ferret his lead was already around 22 minutes.

    The climb that matters more

    The most impressive number may be one of the smaller ones.

    Late in the race came Vallorcine to La Flégère: 10.97 km, +961 m, 1:33:39. Dividing ascent by total segment time gives 616 m/h — a whole-segment descriptor, not his climbing speed, since the section includes flatter and descending ground.

    Beside the earlier 800s and 900s, 616 looks ordinary. But look at when it happened. Dhiman had covered more than 150 km and raced through the night, and around 10 km from the finish, partway up this climb, he tripped on a rock and fell hard. He got up, completed the ascent to La Flégère, and carried on toward Chamonix.

    616 m/h on its own looks unremarkable. What makes it worth noting is where in the race it happened.

    The descents

    Climbing consumes the engine. Hard descending is often what destroys the legs.

    • Col de Voza → Saint-Gervais: 8.28 km, −999 m, 38:53 (≈4:42/km)
    • Grand Col Ferret → La Fouly: 9.7 km, −1,025 m, 46:52 (≈4:50/km)
    • La Flégère → Chamonix: 6.56 km, −857 m, 33:48 (≈5:09/km)

    The final descent was slower — about 10% per kilometre against the early Col de Voza descent. That’s real fatigue, plain and simple. What changes its meaning is the context: seventeen hours of racing, more than 160 km of load, repeated major climbs and descents, and a recent fall. Dhiman was also half an hour clear, while Olson was chasing Chassagne for second and missed him by 46 seconds. Their incentives on that hill were not the same.

    He clearly didn’t descend as fast at the end as he had at the start. What stands out is that the drop-off stayed contained rather than spiralling.

    His cadence across the three went 176, 171, 167 spm. That doesn’t prove his running economy held up: turnover can stay steady even as stride length, ground contact and force production quietly decline. All it tells us is that turnover itself never collapsed, and that’s as far as the number can take us.

    What about his heart rate?

    The heart-rate data is considerably harder to interpret.

    Segment averages range from 112 to 146 bpm. The highest came on more runnable ground — 146 from Saint-Gervais to Les Contamines, 143 from La Balme to Les Chapieux — while two of the steepest climbs read lower, at 119 to Bertone and 128 to Grand Col Ferret. The final descent reads 112.

    It is tempting to call that extraordinary pacing control. I would not. Cold conditions, pole use, wrist movement and changes in sensor contact can all make wrist optical heart-rate data less reliable, and several were present here. The movement trace is much stronger evidence than the heart-rate trace.

    What the data can and cannot support

    The trace is useful. It is not laboratory data, and its own headline numbers do not fully reconcile.

    The reported 169.38 km over 18:14:01 works out closer to 6:28/km than the 6:29 displayed. The 19 segment times do not sum exactly to the total. And the trace’s 169.38 km and +9,843 m sit against UTMB’s official 174 km and 9,700 m.

    Its gradient figures are not elevation gain divided by distance either: 802 m over 5.28 km is about 15% net, while the platform reports 18.1%. That may reflect ascending-only portions, point-by-point sampling, or something else — the method is not published, so those percentages are reported gradients rather than survey measurements. The same caution applies to the distribution table above.

    One recorded kilometre shows 352 m of ascent in 18:56. If both inputs are right, the resulting 1,116 m/h follows arithmetically; the uncertainty is whether GPS distance and elevation are precise enough on that terrain to trust either input.

    The 18:46 it classifies as stopped time is similarly narrow. It means the algorithm rarely registered him as stationary — not that he spent only 18 minutes servicing himself, since a runner can walk an aid station, refill on the move or eat slowly without ever being counted as stopped.

    None of this makes the dataset useless — it just sets the boundary of what it can answer. The trace works well for comparing Dhiman against himself: early versus late, climbing versus descending, steep versus runnable. It’s the wrong tool for pinning down any single metre, second or percentage as exact.

    What he says he built

    Everything above is measurement. This section comes from Dhiman’s own description of his preparation, so it is a different kind of evidence.

    The interesting part is how closely his stated training problem matches what appears in the race.

    His diagnosis came from 2025. Dhiman finished second at UTMB in 19:51:37, but later described himself as having “blown up in the final third.” For 2026, the quality he said he wanted to improve was durability: the ability to keep performing once deep fatigue had accumulated.

    His answer was a large increase in training volume without a similar increase in intensity.

    For six straight weeks before UTMB, he said he averaged roughly 25 hours, 200 km and more than 10,000 m of climbing per week. July alone passed 100 hours of training, versus less than 60 in the same period the year before. He said he deliberately controlled intensity so that he could absorb the larger load.

    The volume had been building much earlier. During the winter, Dhiman reported 305 hours and 170,000 m of vertical gain across three months, much of it through ski mountaineering.

    He also changed how he trained climbing.

    Dhiman said his climbing volume was around 30% higher than in 2025. More importantly, he did much more steep hiking, often with poles and his UTMB kit. He explained that the year before he had treated UTMB too much like a running race and avoided hiking. In 2026, he trained hiking deliberately because so much of UTMB’s climbing would be hiked anyway.

    His racing fitted the same approach.

    At the 90K du Mont-Blanc, he finished second in 9:38:02. He later described the race as preparation rather than an event where he intended to perform at his maximum, fitting the same high-volume approach.

    One of his final hard sessions before UTMB was even more specific: 75.17 km from Chamonix toward Courmayeur, +4,519 m, in 8:18:14. It was another long day on race terrain before tapering.

    None of that proves that a particular training method produced a particular UTMB split.

    But the match is hard to miss.

    He said the weakness was the final third. He trained specifically to remain effective under accumulated fatigue. And in 2026, the most interesting part of his race is exactly what happened after 100 km, then after 150 km: the lead survived, the movement modes remained available, and when Chassagne briefly reduced the gap, Dhiman opened it again.

    Why this performance deserves admiration

    Dhiman did not maintain one pace for eighteen hours. That was never possible on this course. He moved from 4:17/km on runnable ground to more than 11 minutes per kilometre on steep climbing, from cadence in the 170s into the 120s and back again, and his final major descent was slower than his first.

    He fatigued, as any runner would over that distance and terrain. The important part is what remained available despite that fatigue. He could still run when the trail opened, switch to hiking when the grade demanded it, descend after a long climb, and then return to running again.

    That pattern was still visible after 100 km and after 150 km. When Chassagne reduced the lead between Champex-Lac and Trient, Dhiman still had enough to open it again before Vallorcine.

    That matches the problem he said he had tried to solve after 2025. He described himself as having “blown up in the final third,” then built his 2026 preparation around durability, more climbing and much more hiking-specific work.

    He fell late in the race, got back up, completed the remaining mountain section and descended into Chamonix. Second place arrived 31 minutes and 9 seconds later.

    His 2026 time was 1:35:08 faster than his own 2025 UTMB. That comparison is not perfectly controlled: weather and route details differed. But both races bypassed Pyramides Calcaires, and the scale of the improvement is still striking.

    18:16 is the final number. The more interesting story is what was still working when the final third arrived.

  • The Malaysian Heat Strategy: A Nutrition Guide for KLSCM & IRONMAN Langkawi

    The Malaysian Heat Strategy: A Nutrition Guide for KLSCM & IRONMAN Langkawi

    Running a marathon in Berlin or Tokyo is hard. Running one in Malaysia is a different beast entirely. Between the humidity of the KLSCM (Standard Chartered KL Marathon) and the scorching tarmac of IRONMAN Langkawi, tropical heat is a leading reason athletes DNF (Did Not Finish).

    In high humidity, sweat doesn’t evaporate well, so your body temperature climbs and you lose electrolytes fast. Water alone isn’t enough — and overdrinking plain water carries its own risk, including low blood sodium (hyponatraemia), which has been linked to serious harm in endurance athletes.

    Here’s a 2-part heat strategy: manage sodium on schedule, and give your muscles amino acid support once carbs alone aren’t covering a long, hot effort.

    Part 1: Sodium on a schedule with ELEC Stamina

    To manage the heat, it helps to treat hydration (water) and electrolytes (salts) as two separate jobs, not one.

    ELEC Stamina is a swallow tablet made in China, built for heavy sweaters over long sessions.

    • Sodium on schedule: put sodium back on a set rhythm through a long, hot session — it won’t stop a cramp already underway, and cramping has more than one cause.
    • Vitamin B1 and B2 are part of the formula alongside the sodium.
    • Strategy: 1–2 tablets every 10km with water, per the label.

    Part 2: Amino acid support with QC Stamina

    Past roughly 90 minutes of hard effort, if carbohydrate intake isn’t keeping up, the body can start drawing on muscle protein for fuel. That’s part of why a race can start to feel “hollow” late on.

    QC Stamina (Quick Charge) is protein built for use during the race, not after it.

    • Sachet-based amino acid support, light and quick to digest mid-race.
    • Strategy: One sachet of QC Stamina roughly at the halfway point of a long race, or every 2–3 hours.

    The takeaway

    Carbohydrate, fluid and pacing still come first in any race plan. Once those are dialled in, managing your electrolytes with ELEC and your amino acid intake with QC covers the rest of what Malaysian heat asks of you.

  • Katsuo Stamina vs BCAAs: Which Supplement for Endurance Athletes?

    Katsuo Stamina vs BCAAs: Which Supplement for Endurance Athletes?

    Walk into any supplement store and you’ll see walls of BCAA products. They work well for gym training and muscle building. If you’re a marathoner, triathlete or ultra-runner, though, that’s not quite the job you need done.

    Customers ask us this a lot: is Katsuo Stamina just another BCAA? No. Both play a role in recovery, but they’re built for different problems.

    Quick comparison

    What’s the actual difference?

    Traditional BCAAs (branched-chain amino acids) signal your body to build and repair muscle tissue. That’s exactly what you want for strength training or bodybuilding, where the goal is muscle growth.

    Katsuo Stamina works differently. It’s built from bioactive dipeptides — Anserine and Carnosine — sourced from katsuo (bonito), a fish that swims long distances without stopping. These are studied for buffering muscle pH during sustained effort, which is the theory behind delaying the “burn” late in a long race. That’s a different job from muscle growth.

    Which one fits you?

    BCAAs make sense if your goal is muscle mass, your sessions run under 60 minutes and high intensity, or you’re focused on strength training or CrossFit.

    Katsuo Stamina makes sense if you’re training or racing longer than 90 minutes — marathons, triathlons, ultra-running, cycling — and fatigue late in the effort is what’s limiting you.

    Can you use both?

    Yes — plenty of endurance athletes do. BCAAs post-workout for muscle repair, Katsuo Stamina before or during a race. They’re not competing for the same job, so stacking them is straightforward.

    Neither replaces getting your carbohydrate, fluid and pacing right first — that’s still the foundation of any race plan. For endurance athletes training in Malaysian heat, Katsuo Stamina is aimed at a different gap than BCAAs fill, not a replacement for them.

  • Stop Blaming Lactic Acid: How to Turn Your Body’s “Burn” into Fuel

    Stop Blaming Lactic Acid: How to Turn Your Body’s “Burn” into Fuel

    Lactic acid isn’t just waste your body needs to flush out. It’s mostly lactate, an energy source your body can burn or recycle — the burn you feel late in a race comes from your muscles producing it faster than they can process it, not from lactate itself being toxic.

    Every endurance athlete knows the feeling. You’re at the 30km mark of a marathon, or the final leg of a triathlon, and your legs start to feel heavy — like they’re filled with lead. For decades that burning sensation got blamed on one culprit: lactic acid.

    Lactic acid isn’t the enemy

    Older sports science treated lactic acid as a toxic by-product to flush out. That view has shifted — lactate is a genuine energy source. The problem isn’t that your body produces it; it’s that during hard, sustained effort it can produce it faster than it clears it. When that backlog builds, hydrogen ions accumulate, muscle pH drops, and you get that familiar burn.

    Where Katsuo Stamina fits

    Katsuo Stamina is built from Migratory Fish Extract, specifically a peptide containing Anserine and Carnosine, derived from katsuo (bonito) — a fish that swims long distances without stopping. These are studied for buffering hydrogen ions in muscle, which is the working theory behind stabilising pH and delaying the burn during sustained effort.

    It’s aimed at that mechanism specifically — not at masking fatigue the way a stimulant does. No caffeine, no sugar.

    How to use it in a race

    • Pre-race: 4 tablets 30 minutes before the start.
    • During the race: 4 tablets every 90–120 minutes, per the label.

    It’s a peptide supplement aimed at lactate buffering and recovery — not a hydration product, and not a substitute for getting your carbs, fluids and pacing right first.

    [Shop Katsuo Stamina Here]

  • Why Protein Matters During Endurance Events

    Why Protein Matters During Endurance Events

    Past about 90 minutes of hard effort, if carbohydrate isn’t keeping up, your body can start drawing on muscle protein for fuel. QC Stamina is a sachet of amino acid support built to be taken during the race itself, not after it — light, quick to digest, and easy on the stomach.

    Why protein during a race, not just after

    Long-distance running or cycling causes metabolic stress and micro-damage to muscle protein. Consuming protein supports the repair process and helps you adapt to the training load.

    When carbohydrate stores drop — typically past around 90 minutes of sustained exercise — the body can start using amino acids from muscle tissue for energy instead. Providing protein during the event helps reduce how much of that happens.

    General sports nutrition guidance puts daily protein intake for endurance athletes around 1.8 g/kg body weight, with higher needs (around 2.0 g/kg) on low-carb or high-intensity training days. Post-exercise protein, roughly 0.5 g/kg, supports recovery and repair on top of that.

    What makes QC Stamina different from a recovery shake

    • Built for race-day use, not a post-workout shake — light and quick to digest mid-race.
    • Helps sustain muscle output during long efforts when carbs alone may not be enough.
    • Portable sachets — one every 2–3 hours — built to sit easily in a drop bag or race vest.

    It’s protein aimed at a specific job: keeping amino acids available during a long race, once your carbohydrate intake is already covered. It doesn’t replace getting carbs, fluids and pacing right first — those still come first in any race plan.

    QC Stamina fills a specific niche: protein support during long endurance efforts, built to digest easily on the move.

  • 31 Unorthodox Tips for Surviving a Hot/Humid Ultra Trail Race

    31 Unorthodox Tips for Surviving a Hot/Humid Ultra Trail Race

    Running an ultra trail race in Malaysia’s hot, humid conditions is no joke lah. It’s not just about being fit – you need smart preparation, mental grit, and some creative strategies. While standard training advice is good, sometimes you gotta think out of the box.

    In this article, we’ll share 31 tips – some normal, some cham – to help you conquer a humid ultra in Malaysia. From getting used to the heat to staying hydrated, fueling up to cooling down, these tips will give you an edge when things get tough.

    So if you’re ready to level up your humid ultra training, read on for 31 unorthodox tips to help you tahan the heat and humidity.

    Training and Preparation

    1. Simulate race conditions by training in a sauna or steam room.
    2. Run in the hottest part of the day during your training runs.
    3. Wear extra layers to mimic the effects of heat and humidity.
    4. Carry a spray bottle and mist yourself during runs to stay cool.
    5. Train during rainy days to get used to running in heavy rain and mud.
    6. Practice running in wet shoes to prevent blisters and discomfort.
    7. Do HIIT workouts to boost your endurance and heat tolerance.
    8. Train on different terrains like beach, jungle, and hilly areas to prepare for various conditions.

    Pacing and Effort

    1. Run at a ‘lepak’ pace to manage your effort and save energy.
    2. Run by feel, not pace – your body will tell you when to slow down.
    3. Take walking breaks to lower your heart rate and core temp.
    4. Adjust your goals and focus on finishing rather than time.
    5. Embrace the suck and accept that it will be tough.

    Hydration and Electrolytes

    1. Monitor your urine colour – if it’s dark, drink more water.
    2. Drink small amounts frequently rather than chugging at aid stations.
    3. Carry electrolyte tablets and take them with water.
    4. Freeze your water bottles for a built-in cooling system.
    5. Drink coconut water for natural electrolytes and carbs.

    Fueling and Digestion

    1. Eat smaller amounts more often to avoid GI distress.
    2. Experiment with liquid calories like gels and drinks.
    3. Avoid high-fiber foods that can cause bloating.
    4. Bring your own favorite snacks in case aid stations lack variety.
    5. Munch on salted peanuts or keropok for a quick sodium and energy boost.

    Cooling and Protection

    1. Wear a wet bandana or buff around your neck.
    2. Wear a hat with a brim to shade your face and neck.
    3. Use cooling sleeves to protect your arms and keep them cool.
    4. Pour water over your head, back, and chest at every opportunity.
    5. Wear light, breathable fabrics that wick sweat.
    6. Use a combination of sunscreen and UV-protective clothing to shield yourself from the intense Malaysian sun.
    7. Wear polarized sunglasses to reduce glare and eye strain.

    Extra Tips for Rainy Days

    1. Wear a lightweight, waterproof jacket to stay dry without overheating.
    2. Use anti-chafing cream to prevent skin irritation from wet clothes.
    3. Carry spare socks in a waterproof bag to change if needed.
    4. Watch your footing on slippery trails and wooden bridges.

    Remember, every runner different one, so try different things during training to see what works best for you. With the right mix of normal advice and unorthodox tactics, you’ll be ready to tahan your next humid ultra trail race in Malaysia.