Drop in the Excel or CSV file you already keep and get a straight read on your trading. One file, runs on your own computer, and your trades never leave it.
No account. No subscription. Nothing uploaded.
Reads a trade log with one row per trade — not a broker statement that lists each buy and sell on its own line. What works?
All screens on this page show made-up demo data, not real trading results.
The spreadsheet problem
You already log your trades. The answers are sitting in that file — which setup actually pays, which session you'd be better off skipping, whether last month's rough patch was normal or something real.
Getting those answers out means pivot tables, formulas, and an afternoon you'd rather spend somewhere else. The alternative is $29 to $50 every month, forever, to a website that wants your entire trade history sitting on their servers.
LogBench is the third option. You buy it once. It runs on your machine. It reads the log you already have.
What you'll see
Your results split by symbol, setup, session, day of the week, long or short — or any tag you already keep in your own spreadsheet. Every column in your log becomes a table, and the best and worst are obvious at a glance.
Then cross any two of them, like a pivot table: which setup works in which session, which market on which day. Each cell shows how many trades it holds, and a cell with too few trades is greyed out, so you don't read a lucky handful as a result.
Made-up demo data. With your own log, you get a table like these for every column you keep.
Your equity curve in dollars, with the rough patches shaded in, and a bar for every month.
LogBench deals your own trades 5,000 different ways to show how bad a run of bad luck looks for someone with your numbers. Next time you're down, you'll know whether you're inside normal or outside it.
Not just the losses you would have cut — the winners you would have killed on the way. Both sides, in dollars, at four different levels plus one you set yourself.
Mark the setups you saw and passed on, and LogBench keeps a separate scorecard for them. If the trades you skipped are beating the trades you took, that's worth knowing.
Honest numbers
This is the part most tools skip.
If a bucket only has six trades in it, LogBench greys the number out instead of pretending six trades mean something. If the column you picked looks like money moving in and out of an account rather than profit on each trade, it says so instead of building a confident dashboard on top of the wrong number. And when it runs the losing-streak simulation and your real history turns out worse than anything the model produced, it tells you the model lost — instead of quietly reporting a "normal worst case" your own results already blew past.
You can only act on a number you trust. LogBench is built to tell you which ones those are.
Privacy
LogBench is one HTML file. You double-click it, it opens in your browser, and that's the whole product.
What your log needs
LogBench reads a trade log: one row for each trade, with the date and what that trade made or lost in dollars. Have entry price, exit price, and long or short instead? LogBench works out the dollars for you.
One row per trade. The buy and the sell that closed it are on the same line.
| Date | Long/Short | Entry | Exit | Profit/Loss ($) |
|---|---|---|---|---|
| 2026-03-02 | Long | 21450.25 | 21468.50 | 35.26 |
| 2026-03-04 | Long | 21380.00 | 21371.25 | -37.48 |
One row per buy or sell, and no row says what the trade made or lost.
| Date | Time | Symbol | Side | Qty | Price |
|---|---|---|---|---|---|
| 2026-03-02 | 09:41 | MNQ | BUY | 1 | 21450.25 |
| 2026-03-02 | 10:05 | MNQ | SELL | 1 | 21468.50 |
| 2026-03-04 | 11:12 | MNQ | BUY | 2 | 21380.00 |
| 2026-03-04 | 11:40 | MNQ | SELL | 2 | 21371.25 |
Made-up example trades in MNQ futures.
Most broker statements are the second kind. They list every buy and every sell on its own line. LogBench can't pair those lines into trades, and it won't guess. If you load one, it tells you before it shows a single number:
Everything else — symbol, setup, session, stop distance, notes, your own tags — is optional. Add what you have. The more you keep, the more the tool shows you.
A lot of account statements also show money moving in and out of your account. Adding those up gives cash movement, not profit. LogBench warns you about that too, rather than guessing.
LogBench asks which column is which, shows you examples from your own file, and answers most of the questions for you.
Pricing
Checkout is not open yet. It opens soon.
One-time. Not a subscription. 14-day refund, no questions asked. Personal licence for one person. Refund policy · Licence
Questions
No. LogBench reads a file you already keep and does arithmetic on it. It doesn't pick trades, send signals, tell you when to get in or out, or tell you whether to trade at all.
Only if the export has one row per trade, with a date and the profit or loss on it. Most standard broker statements list each buy and each sell on its own line, and LogBench can't pair those into trades — it tells you so rather than guess. Some brokers also offer a closed-trades or realized profit-and-loss report with one row per closed trade; that kind can work. If yours doesn't have one, the capture template is built for exactly this. See what works.
Only to download it. After that, no.
If you have a reasonably current browser, yes. Windows or Mac.
No. You drop your file in and answer a few plain questions about which column is which. LogBench recognises most common layouts on its own.
All work. LogBench asks what a point is worth for anything it doesn't recognise.
It'll tell you why, in plain English, and what to do about it. If it still doesn't work for you, take the refund — that's what the 14 days are for.
“This is the analysis I run on my own trade log, packaged for people who don't want to build it.”