ISODD in Google Sheets: Odd Integers and Alternating Records
Check odd integers in Google Sheets, build explicit whole-ID rules and compare row-based alternation with stable identifier grouping.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: =ISODD(5) returns TRUE and =ISODD(6) returns FALSE. The test is useful for known integer IDs or explicitly defined row positions; it does not replace a separate whole-number validation policy.
Availability and version history
- Introduced: first introduction date is not established by the official history reviewed; no desktop release number is inferred.
- Availability: documented in the rolling Google Sheets service; these examples use the web worksheet workflow.
- Checked: October 14, 2026; official ISODD reference. Documentation and independent models, with no native Google Sheets execution or wider client certification.
Syntax and what the reference establishes
=ISODD(value)
Google describes TRUE for an odd integer or a reference containing one. Its dedicated text does not provide a detailed decimal or nonnumeric conversion matrix. The primary controls below use integers; when a decimal is involved, an explicit TRUNC or INT step supplies the integer being tested.
This is a Boolean test. ODD is a different function that returns a rounded odd integer.
Example 1: signed integer controls
Enter -3,-2,-1,0,1,2,3 in A2:A8 and fill =ISODD(A2) down column B.
| Input | Expected ISODD |
|---|---|
| -3 | TRUE |
| -2 | FALSE |
| -1 | TRUE |
| 0 | FALSE |
| 1 | TRUE |
| 2 | FALSE |
| 3 | TRUE |
There are four odd integers and three even integers. Zero belongs on the even side. A negative sign does not change whether an integer has an odd magnitude.
Example 2: require a positive odd integer ID
In a separate control column enter 5, 5.7, 6, 0, -3, ="5" and =NA(). Apply:
=IF(ISNUMBER(A2),IF(A2>0,IF(A2=TRUNC(A2),ISODD(A2),FALSE),FALSE),FALSE)
Only the numeric integer 5 passes. The decimal is rejected before the parity branch is reached, the nonpositive inputs fail the chosen sign rule, and text or an error fails the type test.
These results belong to the explicit validation expression. They do not certify what bare ISODD would do with the excluded decimal, text or error. A rule allowing signed odd IDs would remove the positive restriction; that is a policy change you can inspect directly in the formula.
Example 3: make decimal handling explicit
=ISODD(TRUNC(5.7))
=ISODD(TRUNC(-5.7))
=ISODD(INT(-5.7))
Expected results are TRUE, TRUE and FALSE. TRUNC gives 5 or -5 by discarding the fractional part; INT of -5.7 gives -6 by moving downward. The parity answers differ because the explicitly constructed integers differ.
Do not read this example as a claim that ISODD itself uses one of those conversion rules on every noninteger input. It shows how to remove that ambiguity from a workbook formula.
Example 4: flag alternating data positions
Put six record names Ash,Beech,Cedar,Elm,Fir,Pine in D2:D7. In E2 enter:
=ISODD(ROW()-ROW($D$2)+1)
Fill down. The positions are 1,2,3,4,5,6, giving TRUE,FALSE,TRUE,FALSE,TRUE,FALSE. Ash, Cedar and Fir are selected under this starting-position convention.
By contrast, =ISODD(ROW()) uses the actual row numbers 2–7 and gives FALSE,TRUE,FALSE,TRUE,FALSE,TRUE. The subtraction and plus-one deliberately set the first data row to position one.
A position-based rule can change a record’s classification after it moves. It does not promise filtered visible-row renumbering. If stable record identity matters, use a validated integer ID stored with the record instead.
Example 5: check a stable-ID alternative
For IDs 301,302,303,304,305,306, =IF(ISODD(id),"A","B") gives labels A,B,A,B,A,B when the placeholder is replaced with each ID’s cell reference. Sorting the records does not change the ID’s parity.
On the seven original signed integer controls, =ISODD(A2) agrees with =NOT(ISEVEN(A2)). That finite complement check is useful for catching a mistaken row origin or an incorrectly copied formula, but it is not a complete type/error proof.
Troubleshooting and scope
Inspect the stored number rather than its rounded display. Confirm whether the requirement concerns an integer’s value or its current row position. Use ISEVEN, ROW and ISNUMBER for those separate questions. Very large numeric identifiers, native decimal coercion and cross-client behavior remain outside these controls.
References and verification
Examples use fictional inputs, English function names and comma argument separators. Expected outputs are independently modeled from the cited rules, not native Sheets captures. Check the spreadsheet locale when reproducing punctuation-sensitive formulas.