Overview
Uses the GMT (Goodman-Martinez-Thompson) correlation constant for accurate conversion. Ideal for educational content, historical research, and cultural applications.
Live Test Mayan Calendar Source →
Formula
One function covers the whole catalog: the first argument names the source, the rest are its inputs, and the "field" pair says which single value lands in the cell. Formulas covers the grammar that applies to all of them.
=VERVE("mayancalendar", A2, "field", "gregorian")=VERVE.CALL("mayancalendar", A2, "field", "gregorian")A2 holds the date you are looking up. Drag the formula down and each row resolves on its own.
With literal values
Nothing has to come from a cell — typed values work the same way.
=VERVE("mayancalendar", "2024-12-21", "field", "gregorian")=VERVE.CALL("mayancalendar", "2024-12-21", "field", "gregorian")Inputs
Required inputs are positional, in the order below. Everything else is passed as a "name", value pair after them — the same shape as SUMIFS. Premium inputs are accepted on every plan but only take effect on plans that include them.
| Input | Type | Where it goes | Description |
|---|---|---|---|
dateRequired | string | argument 2 (A2) | The Gregorian date in YYYY-MM-DD format date |
What lands in your sheet
The "field" pair is what makes the formula resolve to one cell. Its value is a dot-path from the table below, so swapping it is how you pull a different value — one formula per column.
Seeing everything at once
Drop the "field" pair and the formula returns the whole response instead: two columns, field name on the left and value on the right, spilling from the cell you typed in.
=VERVE("mayancalendar", A2)=VERVE.CALL("mayancalendar", A2)The second row's table would land on top of the first's, and every cell after the first reads #REF! (#SPILL! in Excel). Keep one per sheet, or name a field, and leave the cells below and to the right empty.
Response fields
Paths are relative to data. Each one is exactly what the "field" pair accepts, so swapping it is how you pull a different value into a cell. On a plan without a Premium field the cell reads #PREMIUM(field) rather than a value, so a locked field never looks like a real answer.
| Use as "field" | Type | Example cell value | Description |
|---|---|---|---|
gregorian | string | 2024-12-21 | The input Gregorian date in YYYY-MM-DD format |
longCount | object | {…} | |
longCount.formatted | string | 13.0.12.3.3 | Mayan Long Count formatted as baktun.katun.tun.winal.kin |
longCount.baktunPremium | number | 13 | Long Count baktun component (cycle of 400 tuns) |
longCount.katunPremium | number | 0 | Long Count katun component (cycle of 20 tuns) |
longCount.tunPremium | number | 12 | Long Count tun component (cycle of 18 winals) |
longCount.winalPremium | number | 3 | Long Count winal component (cycle of 20 kins) |
longCount.kinPremium | number | 3 | Long Count kin component (day unit in Mayan calendar) |
tzolkin | object | {…} | |
tzolkin.numberPremium | number | 6 | Tzolkin sacred calendar day number (1-13) |
tzolkin.dayNamePremium | string | Akbal | Tzolkin day name from 20-day Mayan sacred cycle |
tzolkin.formatted | string | 6 Akbal | Tzolkin date formatted as number and day name |
haab | object | {…} | |
haab.dayPremium | number | 6 | Haab civil calendar day number (0-19 or 0-4) |
haab.monthNamePremium | string | Kankin | Haab month name from 18-month Mayan civil calendar |
haab.formatted | string | 6 Kankin | Haab date formatted as day and month name |
calendarRoundPremium | string | 6 Akbal 6 Kankin | Calendar Round combining Tzolkin and Haab dates |
daysSinceEpochPremium | number | 1876383 | Days since Mayan creation date (0.0.0.0.0) |
Filling a whole column
Both platforms make one batched call for a column rather than one request per cell, and both cost the same — 2 credits per row looked up. How you write it differs, because the two runtimes batch at different points.
=VERVE("mayancalendar", A2:A100, "field", "gregorian")In Google Sheets, give the arguments ranges and the answers spill down from the cell you typed in. Custom functions there run synchronously and in isolation, so dragged cells cannot be coalesced — the range form is how a column becomes one call. The "field" pair is required here: a per-row two-column table has nowhere to spill. Use a full column per input (A2:A100, not A2) — a single-cell reference is read as row 1 only and the rest of the column comes back blank.
In Excel, type the formula once and fill down — no range form and none needed, because its runtime is asynchronous and the add-in coalesces the calls a fill produces into a single batched request. Do not hand VERVE.CALL a range: Excel flattens it into positional arguments, so A2:A100 arrives as a hundred separate arguments and the cell reads #ERR rather than filling.
Either way, column A holds your date values and the answers land beside them, one row each, blank rows skipped.
When a cell doesn't fill
A failed lookup returns readable text starting with #ERR rather than a spreadsheet error, because Excel cannot show a custom message on a real error — you would get a bare #VALUE! with no reason. The trade-off is that IFERROR() will not catch it; test with LEFT(cell, 4) = "#ERR" instead. Error handling covers the rest.
| Cell reads | What happened |
|---|---|
#ERR Not connected | No API key saved. Open the side panel and connect your account. |
#ERR Replace <name> with a cell or value | A preview formula was copied as-is. Swap the placeholder for a cell reference. |
#ERR No "x" in mayancalendar | An option name this source does not take. The message lists the ones it does. |
#ERR No data point "…" | The "field" path is not in the response. Check it against the table above. |
#PREMIUM(field) | The field exists but your plan does not include it. |
#ERR Out of credits | The cycle's credits are spent. Usage resets on your billing date. |
Before the formula works
The add-in reads the API key you saved once in the side panel — the key never goes in the formula, so a shared sheet does not leak it and a collaborator without access simply sees the last calculated values.
- Install the add-in for Google Sheets or Excel.
- Open the side panel and sign in, or paste a key from your dashboard.
- Type the formula above into any cell.
Use cases
- Educational Tools
- Teach about ancient Mesoamerican calendar systems
- Cultural Applications
- Display Mayan dates for heritage and cultural apps
- Historical Research
- Convert dates for archaeological and historical study
- Novelty Apps
- Generate personalized Mayan birth dates
Other ways to use Mayan Calendar
Set up Mayan Calendar on VerveSheets, or reach the same source a different way. Your VerveSheets account and credits work on all of them — one key, one balance.
Related
More in Reference Data: