Loading player...
If the current server doesn't work, please try switching to another server using the buttons above. Some servers may take a few seconds to load.
If you have been searching for where to watch ONE Friday Fights 170: Yodlekpet vs. Pompet 3 for free, MyFlixer has it ready to stream right now. The 2026 feature movie is available in HD through 9 different servers, so if one is slow you can switch to another without leaving this page.
The cast of ONE Friday Fights 170: Yodlekpet vs. Pompet 3 includes Pompet Panthonggym, Yodlekpet Or.Atchariya, Thway Lin Htet and Xavier Gonzalez. The feature movie was released on September 11, 2026.
Plot summary: ONE Friday Fights 170: Yodlekpet vs. Pompet 3 was a combat sports event produced by ONE Championship that took place on September 11, 2026, at Lumpinee Boxing Stadium in Bangkok, Thailand. A flyweight Muay Thai trilogy between Yodlekpet Or.Atchariya and Pompet Panthonggym headlined the event. The pairing previously to met at ONE Friday Fights 120 in August 2025, which Yodlekpet won by split decision. The second time to met at ONE Friday Fights 126 in September 2025, which Pompet won by split decision.
Every server on this page delivers ONE Friday Fights 170: Yodlekpet vs. Pompet 3 in HD, so choose whichever loads fastest in your region. If you enjoy feature movies like this one, Kickboxer, Never Back Down 2: The Beatdown and Never Back Down: No Surrender are excellent picks to queue up next, and they are all free to stream on MyFlixer.
Yes. ONE Friday Fights 170: Yodlekpet vs. Pompet 3 streams completely free on MyFlixer (also known as MyFlixerz). There is no subscription, no credit card and no account required.
Yes. The servers offer ONE Friday Fights 170: Yodlekpet vs. Pompet 3 in HD quality (720p or 1080p depending on the source) and playback adapts to your connection speed.
ONE Friday Fights 170: Yodlekpet vs. Pompet 3 is a feature film released in 2026.
Switch to another server using the buttons above the player. Most playback problems are solved by choosing a different server or refreshing the page.