Coffee Education8 min read

Development Time Ratio on a Kaffelogic: 75 Roasts of Data

We checked the usual DTR rules against 75 logged Kaffelogic roasts. 86% of the variation in DTR came from which profile was loaded, and our best cups landed anywhere from 10% to 24%.

BrewedLate Coffee

#development time ratio#dtr coffee roasting#kaffelogic nano 7#kaffelogic profiles#roast profiles

Roasting guides give development time ratio (DTR) as a set of bands: under about 10% tastes grassy, over about 25% tastes baked, and filter roasts want something in between. We wanted to know whether that holds on a Kaffelogic, so we checked it against 75 roasts logged on a Nano 7e across six beans and eleven profiles.

The short answer: on a Kaffelogic, DTR mostly tells you which profile was loaded. 86% of the variation in DTR across our roasts came from the profile. Our best cups landed anywhere between 10% and 24%.

If DTR is new to you, first crack in coffee roasting explains what it measures. This post is about what the number does and does not tell you once you start comparing roasts.

Every scored roast, by profile

Cup score vs development time ratio

Each dot is one scored roast on a Kaffelogic Nano 7e: 68 roasts across 6 beans, one roaster.

The dots form vertical bands. Each profile sits in its own narrow range of DTR, and within each band the scores run from poor to excellent.

ProfileRoastsDTR rangeMedian DTRMedian cup score (of 5)
Rich Filter86.5–14.6%8.7%3.5
Gentle Filter710.8–12.5%11.7%4
Bright Filter410.3–12.7%11.8%4
9minFilter69.8–15.7%12.8%3.5
F-WSH 1500-22002212.8–21.9%16.3%3
F-WSH 1000-1700515.3–18.1%17.4%2.5
F-NAT 0-12001117.1–25.3%20.8%4
NordicLight722.1–24.4%23.5%3.5
Raost variants324.3–33.5%26.7%2

Rich Filter at 8.7% and NordicLight at 23.5% have the same median score. Gentle Filter never left a band less than two points wide, yet its roasts scored from 2 to 4.5.

Why the profile sets the number

A Kaffelogic does not hear first crack. Every profile file carries an expected first-crack temperature, and the roast log marks first crack at the moment the bean temperature crosses it. Development time is counted from that crossing. The Kaffelogic log viewer shows the first crack and development time for any .klog you open, with no account.

Profiles put that marker in different places. F-WSH 1500-2200 puts it earlier than Rich Filter or Gentle Filter. A roast that ends at 220 °C has spent much longer above an early marker than above a late one, so the same physical roast would report a very different DTR depending on which marker it was measured against.

One bean, six profiles

The cleanest test is a single coffee roasted on several profiles. This is a washed Ethiopia Sidamo:

ProfileRoastsMedian DTRMedian cup score
Rich Filter27.3%3.25
Gentle Filter312.3%4.5
9minFilter115.7%2
F-WSH 1500-2200316.3%2.25
NordicLight323.3%3.5
Raost Sidamo124.3%2

Read down the DTR column and the scores follow no pattern: the best and the worst results sit next to each other. If you took the F-WSH result at 16.3% and concluded the roast needed more development, NordicLight at 23.3% would seem to confirm it, and Gentle Filter at 12.3% would be the last thing you tried. It was the best cup.

Ethiopia · Sidamo · Washed · 1,400-2,200 MASL · G2 · John Burton

Ethiopia Sidamo ETH04

Goal: origin clarity17 roasts logged

aroma of caramel, lemon flower and spices. Flavours of madeira cake and black tea with lemongrass undertones. Long lemon black tea finish. Crispy acidity, medium coating body. Score: 82.5+

Best so far: Bright Filter at level 2.0, 120 g — tasted good 1 of 1 time.

The journey

  • Tasted good
  • Had a fault
  • Not tasted yet

What the roasts show

  1. Roast 1: 9minFilter at level 2.0, 100 g. 1 with a fault (grassy, roasty).
  2. Then level 2.0 → 1.7, profile 9minFilter → Raost Sidamo: roast 2. 1 with a fault (roasty).
  3. Then level 1.7 → 2.5, profile Raost Sidamo → NordicLight: roast 3. 1 good.
  4. Then level 2.5 → 3.0, load 100 g → 110 g: roast 4. 1 with a fault (grassy).
  5. Then level 3.0 → 2.8, load 110 g → 120 g: roast 5. 1 good.
  6. Then level 2.8 → 2.0, profile NordicLight → F-WSH 1500-2200: roast 6. 1 not tasted.
  7. Then level 2.0 → 2.2: roast 7. 1 not tasted.
  8. Then level 2.2 → 2.3: roast 8. 1 with a fault (grassy).
  9. Then level 2.3 → 2.5, profile F-WSH 1500-2200 → Gentle Filter, load 120 g → 100 g: roast 9. 1 with a fault (sour, roasty).
  10. Then level 2.5 → 2.0, profile Gentle Filter → Rich Filter: roast 10. 1 good.
  11. Then load 100 g → 120 g: roast 11. 1 with a fault (grassy).
  12. Then level 2.0 → 2.2, profile Rich Filter → Gentle Filter, load 120 g → 100 g: roast 12. 1 with a fault (roasty).
  13. Then level 2.2 → 2.0: roast 13. 1 good.
  14. Then level 2.0 → 2.1: roast 14. 1 good.
  15. Then profile Gentle Filter → Bright Filter, load 100 g → 120 g: roast 15. 1 not tasted.
  16. Then level 2.1 → 2.0: roast 16. 1 good.
  17. Then load 120 g → 150 g: roast 17. 1 not tasted.
  • Weight lost: good roasts 9.0%–14.0%, roasts with a fault 12.6%–14.6%.
  • Time in the hot zone: good roasts 1:39–3:00, roasts with a fault 1:49–2:59.
  • End temperature: good roasts 214 °C–223 °C, roasts with a fault 212 °C–224 °C.
  • Good cups were tasted after 10–36 days of rest (6 tastings).

This shows what differed in the roast. It does not say why the cup tasted different.

Recipes tried

  • Bright Filter

    Still dialling in · 3 roasts · 2:40–2:47

    • 2.0 · 120 g · 1 roast, Tasted good
    • 2.0 · 150 g · 1 roast, Not tasted yet
    • 2.1 · 120 g · 1 roast, Not tasted yet
  • Gentle Filter

    Moved on · 4 roasts · 2:23–2:28

    • 2.0 · 100 g · 1 roast, Tasted good
    • 2.1 · 100 g · 1 roast, Tasted good
    • 2.2 · 100 g · 1 roast, Had a fault
    • 2.5 · 100 g · 1 roast, Had a fault
  • Rich Filter

    Moved on · 2 roasts · 2:59–3:00

    • 2.0 · 100 g · 1 roast, Tasted good
    • 2.0 · 120 g · 1 roast, Had a fault
  • F-WSH 1500-2200

    Moved on · 3 roasts · 1:48–1:58

    • 2.0 · 120 g · 1 roast, Not tasted yet
    • 2.2 · 120 g · 1 roast, Not tasted yet
    • 2.3 · 120 g · 1 roast, Had a fault
  • NordicLight

    Moved on · 3 roasts · 1:39–1:49

    • 2.5 · 100 g · 1 roast, Tasted good
    • 2.8 · 120 g · 1 roast, Tasted good
    • 3.0 · 110 g · 1 roast, Had a fault
  • Raost Sidamo

    Moved on · 1 roast · 2:36

    • 1.7 · 100 g · 1 roast, Had a fault
  • 9minFilter

    Moved on · 1 roast

    • 2.0 · 100 g · 1 roast, Had a fault

The recipe that stuck

Profile
Gentle Filter
Level
2.2
Batch
100g
13.9%
2:23
End temperature
221°C
Winning batch
R-094 · 2026-07-14
nice and fruity, smooth, a little darker, could probably be roasted a tick lighter.

Compare two recipes

Comparewith

Nothing differed by more than normal roast-to-roast variation.

  • Hot zone about the same (2:47 vs 2:40)
  • End temperature about the same (223 °C vs 222 °C)

No weight after roasting for Bright Filter at level 2.0, 120 g, so weight lost is not compared.

This shows what differed in the roast. It does not say why the cup tasted different.

What the roasts taught

  • NordicLight ~2.8 / 120g (R-037) first hit “nice and fruity” after rest — early 9min/Raost runs were green or dark-flat.
  • Gentle Filter around 2.2–2.5 / 100g became the cleaner modern lane (R-069, R-094): fruity, no green, watch for a touch dark.
  • F-WSH 1500-2200 at 2.3 was awful underdeveloped on this lot — same family that works for Gatugi is not automatic here.
  • Current fine-tune: Gentle Filter at 2.0 (R-101) after “tick lighter” feedback on R-094.

Where the good cups live

Roast level against batch size. Colour is the profile; a larger dot is a roast that tasted good.

Roast mechanics across the roasts

Roast loss, hot zone and end temperature for each logged roast. Each line has its own scale, so compare shapes, not heights.

Roast goal

Stop roast just after first crack completes to preserve the signature lemon acidity and black tea delicacy. Aim for a light brown color with no oil development. Focus on highlighting the madeira cake sweetness while maintaining the crispy, bright character that defines high-altitude washed Ethiopians.

Do the textbook bands hold?

Partly.

  • Over 25%: yes. Four scored roasts ran above 25%. They scored 1.5, 1.5, 2.5 and 3.5. None was a cup we would repeat.
  • Under 10%: no. Six scored roasts ran below 10%, five of them on Rich Filter. They scored between 2 and 4.5, with a median of 3.5. One of our twelve best roasts had a DTR of 9.8%.
  • A target range: no. The eight best-scoring roasts with a logged DTR (4.5 or higher) had DTRs of 9.8, 10.3, 12.0, 12.2, 14.3, 15.4, 19.7 and 24.2%.

Across all 68 roasts with both a score and a DTR, the correlation between the two was weak and negative (r = −0.29). After removing each profile's own median it was weaker still (r = −0.18).

Where DTR is useful: inside one profile

On a single profile the marker stays put, so DTR means something. What it mostly means is the level you chose. Across 21 roasts on F-WSH 1500-2200, level and DTR moved together almost exactly (r = 0.95), from about 15% at level 2.0 to about 20% at level 3.0.

On that profile, lower was better for the washed coffees we ran through it: roasts scoring 4 or more had a median DTR of 14.9% at level 2.0, and roasts scoring 2.5 or less had a median of 17.4% at level 2.45. That is a usable rule for that profile and those beans. It does not carry over to another profile.

How to use this

  • Compare DTR only between roasts on the same profile. There it is a quick check that a level change did what you expected.
  • When you switch profiles, start again. A 12% on Gentle Filter and a 12% on F-WSH 1500-2200 are different roasts.
  • Across profiles, compare what does not depend on the marker: drop temperature, total time, roast loss and, above all, the cup.
  • Treat published DTR bands as belonging to the roaster and profile they came from. The over-25% warning held up for us. The under-10% one did not.

These are one roaster's logs and one palate, with a handful of roasts on most profiles, so read the scores as directional. The full attempt history for each bean is in the roast logs.

Free for Nano owners

See your own DTR by profile

Upload your Kaffelogic .klog files and BrewedLate works out first crack, DTR and roast loss for every batch, grouped by bean and profile.

Related Reading

Frequently Asked Questions

What is a good development time ratio on a Kaffelogic?
There is no single good number, because DTR depends on the profile. In our logs the best cups came at about 12% on Gentle Filter, 15% on F-WSH 1500-2200, 20% on F-NAT 0-1200 and 24% on NordicLight. Find the DTR that tastes right on one profile and compare only against other roasts on that same profile.
Why is my DTR so low on Rich Filter?
Rich Filter puts its first-crack marker later in the roast than the F-Series profiles do, so less of the roast is counted as development. Rich Filter had a median DTR of 8.7% in our roasts and still scored a median 3.5 out of 5, the same as profiles running above 20%.
How does a Kaffelogic calculate development time?
The roaster does not hear first crack. Each profile file has an expected first-crack temperature, and the log marks first crack where the bean temperature crosses it. Development time is the time from that crossing to the end of the roast, and DTR is that time divided by total roast time.
Is a DTR under 10% always underdeveloped?
Not on a Kaffelogic. Six of our scored roasts had a DTR under 10%, five of them on Rich Filter, and they scored between 2 and 4.5 out of 5 with a median of 3.5. The low number reflected where the profile puts its first-crack marker.
Does a higher roast level increase DTR?
Yes, on the same profile. Across 21 roasts on F-WSH 1500-2200 the level setting and DTR moved together almost exactly, from about 15% at level 2.0 to about 20% at level 3.0. On one profile, DTR is mostly the level setting expressed as a percentage.

Related Articles