The Friday Number

The Friday number: £300 to Thailand this week

On £300 to a Thai baht bank account this Friday morning, Instarem arrived at the top: THB 13,245.22 (about £300) for a zero fee. Wise came in £1.47 behind, all of it in the £3.38 fee. Skrill's zero fee is a lure, its rate about 2 percent below the real one, worth roughly £6 on this send. NatWest and Nationwide sat £5 and £19 behind.

#AppArrives asBehind the top

1InstaremTHB 13,245.22Most arrivesBest on today's table. No fee, rate about 0.6 percent below the real rate.

2WiseTHB 13,179.86THB 65.36£1.47 behind Instarem on £300. Wise gives you the real rate; the £3.38 fee is what puts it second.

3SkrillTHB 13,066.93THB 178.29No fee on the screen. The rate sits about 2 percent below the real one, which costs roughly £6 on £300.

4NatWestTHB 13,023.55THB 221.67No fee, but a rate about 2.3 percent below the real one. About £5 behind Instarem.

5RemitlyTHB 12,907.94THB 337.2899p fee and a rate about 2.9 percent below the real one. About £7.60 behind Instarem.

6NationwideTHB 12,394.31THB 850.91£15 up-front fee plus a rate about 2.1 percent below the real one. About £19 behind Instarem.

What to actually open

If you already have Instarem installedUse Instarem.On £300 this morning it delivered 13,245.22 baht for a zero fee. That was the best of the fresh prices on the Wise price comparison for Thailand today, about £1.50 ahead of Wise and about £4 ahead of the next app.

If Wise is the one you already useWise is a fair pick.On £300 Wise delivered 13,179.86 baht after a £3.38 fee, about £1.47 behind Instarem. Wise gives you the real exchange rate, the one you see if you search "1 GBP to THB" on Google. On Thailand this morning that put Wise second by a small margin. The reason is the fee, not the rate.

If you reach for Skrill because it advertises no feeKnow what you are paying.On this route Skrill's rate sits about 2 percent below the real one, which on £300 is about £6 the app keeps in the exchange. The arrival of 13,066.93 baht is about £4 behind Instarem on the same send. A zero fee on the screen is not the same as a zero cost.

Do not open your Nationwide app for this.On £300 the Nationwide send delivered 12,394.31 baht, about £19 less than Instarem for the same money going to the same baht account. Part of it is the £15 transfer fee the bank charges up front; the rest is a rate about 2.1 percent below the real rate. NatWest does not charge the £15 fee, but its rate still sits about 2.3 percent below the real one, which on £300 is about £7 the bank quietly keeps.

Catches

A few things to check before you send. The table above is a bank deposit into a Thai baht account. If your family wants cash to collect at a Western Union counter or a 7-Eleven branch in Thailand, the price is a different one. Open the app and check the receiving screen before you send.

Several apps that senders to Thailand reach for did not return a fresh price for GBP to THB on the Wise price comparison this morning. That group includes Revolut, Starling, Monzo, Chase, TransferGo, LemFi and Small World. HSBC, Barclays, Lloyds and Santander appeared on the feed, but with prices last pulled on Monday. They are missing from the fresh table today, not judged. If one of them is your usual app, open it and check the number yourself before you send.

Timing matters on Thailand. Thailand is six hours ahead of the UK while the UK is on summer time, so a Friday morning send from London reaches Thai working hours mid-morning in Bangkok. Several of the bank rows on the Wise price comparison for Thailand were last pulled on Monday, so the live price on your bank's app may differ by the time you open it.

How we checked

The check ran Friday 9 October 2026, morning UK time. Prices come from the Wise price comparison for a £300 bank transfer to Thailand, pulled Wise at 04:05 GMT, Instarem at 02:45, Skrill at 03:31, NatWest at 03:30, Remitly at 03:40, Nationwide last night. An independent feed matched Wise's rate within 0.2 percent. Raw JSON on file.

Corrections

None so far. If we get something wrong, the fix is dated here.