Göteborg-Majorna OK · Season report

Tisdagsmat 2026:
who cooks, who eats

Twenty Tuesdays, 13 January to 26 May. Every sign-up comment read and attributed, every alias untangled, every avanmälan subtracted — and the cooking rota set against it.

20Tuesdays
843comments read
123distinct eaters
1 032portions ordered
39people / Tuesday
The season Steady at ~50, with three sharp dips 20 Tuesdays · 1 032 portions

Each bar is one Tuesday. The dark part is how many people signed up; the light part is the extra portions they ordered on top — partners, kids, a second helping.

People signed up Extra portions Pink dates = the three big dips

The floor sits around 45–60 portions. The three dips — 10 Feb (20), 7 Apr (24) and 12 May (30) — line up with the winter sports break and the Easter holiday week; the May dip has no obvious holiday behind it. Peak night was 5 May: 52 people, 69 portions.

The cooking rota Every Tuesday had a named cook — and nobody cooked twice 34 cooks · nobody twice

Each event page names the cooks (Dagens matlagare, once Ansvariga). Across 20 Tuesdays that is 34 named individuals across 17 pair-nights plus 3 family teams — and not a single repeat. The rota is perfectly even.

DateCooksPortions

The finding that matters: cooks almost never sign up for the food they make. Of the 34 individually-named cooks, only three left a sign-up comment on their own night — Fredrik Hamrefors (20 Jan), Johan Olson (24 Mar) and Amelie Josefsson (19 May) — plus Klara and Nils on the Wallinder family night. So every Tuesday's real headcount is roughly two higher than the comments suggest, and about 40 meals across the season are invisible in this data.

Two people cooked but never once signed up to eat all season: Robbie Andersson (24 Feb) and Linnéa Golsäter (14 Apr). They appear nowhere in the leaderboard below.

Ate a lot, never cooked

Ten portions or more across spring, no turn on the rota. Number shown is portions.

Cooked, ate little

Took a turn at the stove but ate six portions or fewer — the last two never signed up at all.

Every eater All 123 — click any row to see their entries 123 people · expandable rows

Visits counts Tuesdays a person signed up and did not cancel. Portions is how much food that added up to; a pink chip flags people who routinely order for more than themselves. Expanding a row shows every comment they left, what it was worth, and which ones did not count.

#NameVisits (of 20)PortionsCooked
Identity matching The same people, wearing different names 134 addresses → 123 people

The raw data had 134 email addresses and far more display names than there are humans. Matching went on the comment author's email first, then on the name — and the two disagree often enough to matter. Merging changed the leaderboard: Philip goes from 9 visits to 13, Thelma from 4 to 8.

Nicknames & short forms 34 MERGED

Same inbox, different signature. Two share no letters with the real name at all.

    One person, several inboxes 12 MERGED

    Caught by name, since the addresses look unrelated. Three are typo domains that would otherwise split a person in two.

      Look-alikes kept apart 4 TRAPS

      These would merge on name alone. Different addresses, different families — so they stay separate.

        Corrected: Jonas Egger and Jonas Holer were listed here as two people. They are one — Jonas took the name Holer when he married, and kept posting from both addresses. Now merged: 8 Tuesdays, 8 portions.

        Shared family inboxes 2 SPLIT

        The opposite problem: one address, several eaters. Counted as separate people, not one very hungry one.

          Who belongs together Households, and why the sign-ups hide them 14 households

          You named six couples. Working outward from those, the data confirms several more households — and, more usefully, shows that a couple usually appears as one order of ×2, not two orders of ×1. That has a direct consequence for the rota, below.

          Couples you confirmed 6

          Five of the six also cooked together as a pair — the rota is quietly built out of couples.

            Households the data proves 5

            From a shared inbox, a shared surname, or one member naming the others in a comment.

              Families, confirmed by you 4

              Flagged from shared surnames and separate addresses; you confirmed all four.

                Cooked as a pair, relationship unknown 12

                The remaining pair-nights. Given five of your six couples cooked together, some of these are probably couples too — but plenty will just be friends or training partners.

                  Two ways a couple shows up — and why one of them is invisible

                  The six confirmed couples split cleanly into two behaviours, and it explains a lot of the odd numbers in the leaderboard.

                  CouplePatternShared TuesdaysPortions each

                  Martin Ahlberger and Klara Yngvesson never once signed up on the same Tuesday — they take turns ordering ×2 for the pair. Sebastian Inderst orders ×2 fifteen times while Anna Caglio appears twice; Fredrik Hamrefors the same against Alva Svensk. So a name with a high portions-per-night figure is usually one person carrying a household, and their partner's own count is near-empty.

                  What did not work

                  I tried to find couples statistically, by looking for people who turn up on the same Tuesdays more often than their attendance rates predict (a phi coefficient over all 7 503 possible pairs). It fails completely. Your six couples land at ranks #75, #461, #921, #3699, #6348 and #7456 — spread across the whole range, with Martin and Klara coming out as the 48th least co-occurring pair in the club. Co-attendance measures the opposite of what you'd hope: the couples who share an order look like strangers, and the pairs at the top of the list are simply people who both attend most weeks. I am not offering that list as couple candidates, because it isn't one.

                  What does carry signal: a shared inbox, a shared surname, one person naming another in a comment, and — for this club specifically — being rostered to cook together.

                  How the count was made Judgement calls worth knowing about 6 judgement calls
                  1. Cancellations subtracted. 22 sign-ups were withdrawn — avanmälan, avbokar, återbud, "blivit sjuka". If a person's last word on a Tuesday was a cancellation, that Tuesday does not count for them.
                  2. Two comments landed after their own event and were excluded, both six days late and clearly meant for the following Tuesday: Nils Kristian Kumar (17 March) and Patrik Falk (14 April).
                  3. Corrections respected, not added. "Justerat till 2 st mat" replaces the earlier order rather than adding to it; "1 avanmälan" subtracts one portion without voiding the night; "Ta bort en mat" likewise.
                  4. Double posts removed. Kristoffer Sideby re-posted the same order on 5 May ("Råkade svara på en annan kommentar. Så gör det igen"), and Edvin Nilsson submitted twice in the same minute on 3 Feb. Counted once each.
                  5. Nine comments were adjudicated by hand because no rule reads them correctly — "Mat till Elsa, Hanna och Andreas" is three portions, "3x mat + 2barn" is five, "August (8 år) och jag" is two. Each is labelled manual in the expanded rows.
                  6. Not included: whether anyone actually showed up and ate — and, as above, the cooks themselves.

                  Cross-check: the figure for 17 March — 44 people, 63 portions — matches a hand count of that event's 50 comments.

                  Planning the autumn Six suggestions, drawn from what spring actually did v34 – v52 · drag & drop
                  1. Draft cooks from the people who ate the most food but never cooked — rank by portions, not Tuesdays. A person who orders three every week creates three times the work of a solo eater, so portions is the honest measure of what someone owes back. It reorders things: Joakim Frid came only 6 Tuesdays but ate 18 portions, and Jani Katajamäki 7 Tuesdays for 17 — both ahead of people who turned up twice as often and ate alone. Spring had 34 individual cook turns against 123 eaters, and 81 people never cooked once. Autumn opens in week 34 — Tuesday 18 August — and runs to 22 December: 19 Tuesdays, of which the last is the Julbord and needs no cooks. That leaves 18 cooking nights, 36 slots. The 36 biggest never-cooked appetites fill them, with 45 more in reserve. That is the rota pre-loaded below.
                  2. Publish all 16 nights at once, with cooks named, before the season starts. Spring did this — every event was created on 25 October 2025 — and it worked: nobody cooked twice and no night went unstaffed. Keep it, and let people swap between themselves as long as the swap is written in a comment.
                  3. Count the cooks. Only 3 of 34 cooks signed up for the food they made, so roughly two people per night ate without appearing anywhere — about 40 meals across spring. Either ask cooks to sign up like everyone else, or just add 2 to whatever the comments say.
                  4. Plan 55–60 portions on a normal Tuesday, ~25 on a holiday week. Spring's median was 57 and the mean 52, but the average is dragged down by three holiday nights. Autumn's obvious dip is 27 October (höstlov, week 44) — flagged in orange below. The two August Tuesdays land at the tail of the summer holidays and will likely run thin too, so treat 18 and 25 August as ~25 rather than 55. Expect the last night or two before Christmas to soften as well.
                  5. Fix the sign-up format — this was the single biggest source of error. Ask for Mat x2 (a number every time, even for one), diets in parentheses, and the bare word Avanmälan to cancel. Free text cost real accuracy: "Mat x 3 (1veg)" read as one portion, "Mat tack x2" as one, "Återbud" wasn't recognised as a cancellation at all.
                  6. State a deadline and hold it. Two people commented after their event had happened, and several of the 22 cancellations arrived the same afternoon. A stated cut-off — Monday 20:00, say — makes the shopping number trustworthy.

                  The ten who owe the club a dinner

                  Most food eaten, never once on the rota — ranked by portions. These are the first names to ask. The last column is portions per Tuesday: anything near 3 is a household, not a single plate.

                  #NamePortionsTuesdaysPer night

                  A draft rota you can rearrange

                  Eighteen cooking nights, two cooks each, ordered so the heaviest appetites cook first — plus 22 December, the Julbord, which takes no cooks. Your two August Tuesdays start empty, so drag people in or press Fill with suggestion to re-deal the whole season. Households are kept together by default — a couple takes a night as a pair, and the green figure on each card is the portions that pair ate between them in spring. Solo cooks are paired with the next solo down the list.

                  Drag a name into a slot, between slots, or back to the pool — or tap a name and then tap a slot, which also works on a phone. The reserve list is searchable and grouped by household, so partners sit next to each other with their joint total; ♥ marks anyone who belongs to a household. Turn the ♥ button off if you'd rather place people individually. Add anyone who isn't in the spring data — new members, guests — with the field under the reserve list; they start at 0 portions and can be removed again with the ×. Your draft is kept in this browser, so you can come back to it.

                  Only people who never cooked in spring are in the draft. All six confirmed couples already took a turn, so they start in the reserve list rather than on the rota — Fredrik Hamrefors + Alva Svensk cooked on 20 January, and at 28 portions between them they would otherwise sit joint-third heaviest in the club. Drag them in if you want them back on.

                  Reserve list

                  Everyone not currently rostered, most food first. p = portions, d = Tuesdays.

                  ♥ 28p household joint total ↺ 20 Jan already cooked this spring

                  New members and guests aren't in the spring data, so they start at 0 portions.