68-65: UE Lady Warriors End a 31-Game Drought, but the Scoresheet Still Owes One Point

At the SMART Araneta Coliseum in Quezon City, the big board on Wednesday night read 68-65, and the University of the East bench had already emptied. For the first time in two years, the UE Lady Warriors walked off a basketball court counting a win instead of a loss. Thirty-one games. Thirty-one straight defeats. A first victory since September 22, 2026. By the end of the UAAP Season 89 fixture, La Salle had the ball, the clock was short, and the gap was three points.

When I added the individual lines on the scoresheet, the board and the paper disagreed by one point. Sy Oñate 25, Rachel Lacayanga 18, Buscar 5, Lumibao 5, Vacalares 4, Ronquillo 3, Gutierrez 3, Sajol 2, Guillim 2, Ramos 2. The sum is 69. The team total is 68. La Salle's lines add up cleanly to 65. So on the night UE ended a 31-game drought, its scorecard left a one-point balance outstanding.

The match is a ledger before it becomes a story. And a ledger does not close until both columns agree. This report will therefore do two things at once: give the accounting for a win that is real, and ask for the accounting of the one point that has not yet arrived.

Context: thirty-one games, two years, one date

UE's name in UAAP women's basketball has been attached to one thing for several seasons now — a losing run. In Season 89 the team's record stands at 1-7. La Salle is also 1-7. This was not a fight for the top of the table; it was two teams starving for a single win. That is why it became news — not the score, but the snapping of the sequence.

The headline put the word "finally" first. That choice is not wrong. After thirty-one losses, a win is not a routine result; it is an event. But as a journalist I also have to record that the event was one-sided. There were quotes from head coach Ian Valdez, a quote from Rachel Lacayanga, a date, numbers. There was no voice from La Salle — no coach, no player, no explanation of how they closed so late.

In my own file there is a category I call the milestone game. In these, the result is larger than the story, and that is exactly why the most holes get left in them. In 2026, when I left the print desk with a hard drive holding 1,180 hand-coded games, the first rule I set was that in a milestone game the ledger is opened first, not last. Because on the night the emotion is highest, the arithmetic is weakest.

That is what happened here.

The ledger opens: 43 points, ten scorers

The first question I ask any box score: who made the score, and who made it possible. UE's sheet carries ten names. Ten players scored. That is good news in itself, because teams that have lost thirty-one games usually compress their scoring into one or two names while everyone else stops wanting the ball. That did not happen.

But the second question matters more. Forty-three points came from two people — Oñate's 25 and Lacayanga's 18. Between 62 and 63 percent of the total. The team showed depth, but it placed the responsibility for winning on two sets of shoulders. The other eight players produced 26 points if the total is 69, or 25 if the total is 68. I will return to that one point, because it is the most honest part of this report.

The La Salle lines I have add up to the team's 65. That sounds technical; it is not. When one team's sheet balances and the other's does not, the first thing settled is which piece of paper you trust. La Salle's paper is clean. UE's paper owes one point. That does not diminish the win. It leaves the document of the win unfinished.

The margin is three. That one point, still unattributed, would make the gap four if it belongs to UE, two if it belongs to La Salle, and would change the final score entirely if it belongs to neither. One point of detail, three different games.

In the college and school games I have watched over the years, one thing recurs: on the night a team breaks a long run, the game on the floor is a three-point game and the game on paper is a four-point game. This is not a mystery; it is the ordinary cost of manual scoring. The real question is whether that cost is acknowledged or buried under the beauty of the story.

What the scoresheet does not say

Here I have to open a page against my own model.

All I have is the final score, individual points, team records, and the fact that La Salle rallied late. I do not have a shot map, a possession count, turnover figures, free-throw rate, or a reliable quarter-by-quarter breakdown — the quarter scores given appear to be cumulative rather than per-quarter. Cumulative figures read easily and analyse badly, because they cannot tell you who won which quarter. Basketball games are often decided in one quarter, and a sheet that does not show that quarter is telling half the story.

Which means I cannot build a possession-level reconstruction of this game. I cannot tell you UE's offensive rating or its shot-quality index. If I invented those numbers, this report would die the moment a reader asked for the source.

Seventy-two hours is enough to rebuild the numbers, not the myth. But that requires the full sheet, and here it is not present. So I will do what few in my trade do: draw conclusions only from what is visible, and leave blank what is not.

So what is visible? A team scored 68 points and 43 of them came from two players. Ten players scored, which means the ball moved. The opponent stopped at 65 and came back late, which means the game was alive to the end. The margin was three, which means a single changed call could have flipped the result.

What is not visible is what kind of win this was — defensive, offensive, or simply a night when the other team made two mistakes in the last two minutes. That is the difference between a report and an analysis.

The fourth quarter: who held the filter

Spain had the volume; Russia had the filter. The 2026 World Cup match in Moscow taught me that sentence, and since then I separate two things in every sport: who generated the most chances, and who decided which chances counted.

I do not have the data to apply the full formula here, but a limited claim can be made. La Salle rallied late, which means UE led for most of the game and had to protect a lead at the end. Protecting a lead is a separate skill. A team that has lost thirty-one games usually does not have it — it folds in the last five minutes, misses free throws, gives the ball away, and the board moves past it. That did not happen.

That is the real data point of this win, and it is not written in any column of the box score. It is written in what did not happen.

I call this the non-event. In my database every team has a column for the things it did not do in the final three minutes. UE gets three entries on this night: did not surrender the lead, did not foul needlessly, did not panic. None of the three can be proved from a statistic, and without all three the win does not exist.

My old rule is to pair every model with a document. Here there is no model, so the document is everything — and the document is incomplete. Until the official UAAP sheet or the team record book surfaces, the 31-game streak is also a claim, not a datum.

Let me be clear: I am not saying the thirty-one is wrong. I am saying that in this report the source behind it is not recorded. I learned to ask every transfer rumour for a receipt and a timestamp; every streak should be asked the same. The date of September 22, 2026, the figure of thirty-one, the reference to "two years" — those three do not fully reconcile. If the last win was in September 2026 and Season 89 is now being played, the interval sits short of two years. It may be that the interval is right and my count of seasons is off. Either way, the discrepancy belongs in the copy, because the kind of record it is depends on it.

One more inconsistency: the name

One reference spells the player "Aliyah Ronquilo"; the box score spells her "Ronquillo." These are almost certainly the same person, but assuming is not reporting. If a sheet cannot hold a name steady in two places, what guarantee does it offer on the points?

This is small, and I know small things do not stop readers. But a data journalist's job is to collect the small things that weaken the big arithmetic. One misspelling is not a crisis. One misspelling plus a one-point gap plus a missing date plus cumulative quarter scores becomes a pattern.

The pattern is called haste. And the cure for haste is not blame; it is process. My desk runs three coders, fixed field names, and a Monday audit. Any claim I cannot rebuild from my own database within an hour is killed by me before an editor sees it. Apply that rule here and the 68-versus-69 argument is settled before publication.

Contrarian: a three-point win is not a structure

Now the part where I have to fight my own habit.

Base rate first. The base rate is this: most teams that break a long losing run lose again within the next few games. Breaking a streak is an event; improvement is a process; several months usually separate the two. I am writing this first so that I do not join the crowd that treats one win as a turning point.

This win came by three points against a team that is also 1-7. There was no top side across the floor. It is not a result that proves UE's problem is solved. What was solved is that the team won a close game, and winning close games is a distinct skill that thirty-one losses may have buried somewhere.

The reverse is just as true, and it is my real point. I do not treat thirty-one losses as a structure either. A long run does not by itself say how bad a team is; it says only how many close games it lost in a row. Teams that lose close games are often not very bad — they simply make the most mistakes in the last two minutes. This time the team did not make them, and the result changed.

That is where correlation and causation part. The cause of the win is not "the team changed." The cause is probably that two or three things which broke in the last five minutes of the previous thirty-one games did not break this time. That is a very small change, and very small changes are often the largest difference on a scoreboard.

I learned that in 2026, when my model broke inside the Orlando bubble. Home-team win rate fell from 55.3 percent to 50.1, and I had seventy-two hours to rebuild everything. The lesson was that when a variable changes — whether it is a crowd or a fear in the last five minutes — you rewrite the conclusion, not the model.

Receipt and timestamp: what is raw in this story

Now the plain version.

In its original form this is a good milestone story: fast, clear, kept alive by the coach and a player, and focused on the right subject. It is read for the thing such stories are read for — relief. Two years of losing, then a win, and a win protected in the last minutes. As narrative, it works.

But if I file it in my database, three flags go up.

First, the scoring sum. 69 versus 68. It is a one-point gap and the fix is simple: get the official sheet, correct one player's total, and the story is clean. Until then, every sentence that says "68 points" rests on an unfinished document.

Second, the date. The story carries a weekday, not a full date. For a game result that is a significant gap, because the value of such a story lies in its freshness.

Third, sourcing. The thirty-one games, the September 22, 2026 date, the 1-7 records — none of these carry an explicit source. Records and streaks should come from a team or league record book, and that book is their receipt.

I do not call these the writer's errors, because in sports journalism this is normal — you come back from a venue and file within the hour, and the sheet is often still in transit. But a data journalist's job is to say that normal and true are different things.

In the story and missing from it

The report tells us UE won, the streak broke, the coach spoke of sacrifice and follow-up, Lacayanga spoke, and La Salle rallied late.

It does not tell us why UE lost thirty-one games. It does not tell us what the win does to the standings beyond both teams being 1-7. It does not tell us what La Salle's coach was thinking as his team climbed back from four or five down in the closing minutes. It does not tell us how UE built the lead — an early surge, a second-quarter run, or exploitation of La Salle's foul trouble.

I also do not know whether La Salle was favoured. If it was, this is an upset and the news value doubles. If the teams were level, this is a target met. Readers should feel different things in those two cases, and the story gives them one feeling.

On top of that, there are quotes. Ian Valdez speaks of sacrifice and follow-up; Rachel Lacayanga is quoted alongside. The quotes are good. But a coach's quote does not tell you how many offensive rebounds his team took in the third quarter. A coach's quote tells you intent, not performance. The two should be kept apart, and in this story they sit together.

A wider lens: who this win is for

I have an old argument to make here, and I am making it because it is true, not because it is my habit.

One win in one UAAP women's basketball game, and a story about thirty-one losses, will draw more discussion than the league those games are played in. I will not repeat that the NBA lens distorts everything; I will say it once and move on to the domestic ledger, because that is where the real story is.

The real story is that a team won one game in two years and that became news. That is itself a statistic — it tells you how thin the competitive balance is. In a league where a team can lose thirty-one straight and its single win becomes a story, the talent gap is very wide. That gap is not closed by a coach's sacrifice. It is closed by scholarships, court hours, and junior feeder systems — the things that never make the story.

I grew up covering basketball in India, where the game lived inside Railways, Services, banks and public-sector units. There I learned that the pyramid is built by employers and schools, not by owners. Philippine college basketball runs on a similar institutional frame, and so the question is the same: when a team loses thirty-one games, the answer is not in the coach's resignation, it is in the scholarship budget. No coach, however much he speaks of sacrifice, can save a roster that turns over every year.

That is the structural point missing from this story — because the cause of thirty-one losses sits in the system more than on the floor.

What to watch next round

UE's next game is the first test of what this win was. If the same thing shows up again — the patience to protect a lead in the last five minutes — it is a beginning. If the team reverts, it was one night.

Three signals for me. First, the 43-point concentration. If more than 60 percent of scoring stays with Oñate and Lacayanga next time, the depth is on paper only; if it drifts toward 50, the team is genuinely changing. Second, the last-five-minute free-throw rate. The signature of teams that lose thirty-one games is that they cannot make the ball go in from the line at the end. One game proves nothing; three games make a pattern. Third, and most important, the sheet. Next time UE plays, the individual points should add up to the team total. It is a small thing. But when a team wins after two years, the first proof of that win should be its scoresheet, not its headline.

I have killed two columns in my career because they could not clear a new filter, and one of them was mine. This report belongs in that category. It is a real win, written on an unfinished document. Both things are true at once, and printing both at once is the minimum standard of the trade.

The board says 68-65. The ledger says 69-65. After thirty-one losses, that gap will stop nobody — but it exists, and what exists gets counted. The next time a team ends a thirty-one-game run, the first question will be the same: on which piece of paper?

One question for the reader: if a report on a single win cannot balance its own score by one point, on what basis do we accept the rest of what it says — the coach's quote, the player's courage, the two-year wait? The next era of sports journalism will start from the scoresheet, not the stands.