Count a specific weekday in a year from an ISO date

The calculator validates the complete date, extracts its year, and applies Gregorian calendar rules with deterministic integer arithmetic. It never depends on the machine clock, locale settings, daylight-saving changes, or a runtime date parser. The result includes the normalized weekday, count, leap-year status, year length, and weekday of January 1, making the answer easy to inspect or automate.

Provide an explicit date and weekday

Send a date written exactly as YYYY-MM-DD and a weekday name such as Monday, Tuesday, or Friday. The date is explicit because it determines the calendar year to examine; its month and day do not limit the counting interval. For example, both 2024-01-01 and 2024-11-30 select the complete 2024 calendar year. The full date must still represent a real Gregorian day, so impossible inputs such as 2023-02-29 or a thirteenth month are rejected instead of being silently normalized. Weekday names are matched without regard to letter case, and familiar three-letter English abbreviations such as Mon, Wed, and Sat are accepted. The response repeats the original date, identifies the selected year, normalizes the weekday to its full English name, and reports a Sunday-origin weekday index. Requiring these two clear inputs prevents hidden dependence on the current date and makes stored requests reproducible long after they were created. It also keeps the API suitable for forms, scheduled jobs, spreadsheets, and audit records where an implicit year would be ambiguous.

Understand how the deterministic count works

Every ordinary Gregorian year contains 365 days, which is exactly 52 complete weeks plus one additional day. A leap year contains 366 days, or 52 complete weeks plus two additional days. Therefore every weekday occurs at least 52 times. In an ordinary year, the weekday on January 1 occurs for a fifty-third time. In a leap year, the weekdays on January 1 and January 2 each occur 53 times. The calculator first applies the Gregorian leap-year rule: years divisible by four are leap years, except century years unless they are also divisible by 400. It then computes the weekday of January 1 using bounded integer arithmetic and checks whether the chosen weekday falls among the one or two additional days. No JavaScript Date object is constructed. That choice avoids implementation-dependent parsing, host time zones, daylight-saving transitions, and locale behavior. The returned year length, leap-year flag, and January 1 weekday expose the key facts behind the answer, so a count of 52 or 53 can be checked without treating the endpoint as a black box.

Use the result in planning and validation

A weekday count is useful whenever a yearly estimate depends on a recurring weekly event. Payroll teams can establish the number of regular Friday pay dates before accounting for holidays. Operations teams can estimate Monday opening days, schools can measure potential teaching weekdays, and analysts can validate calendar dimensions generated by another system. Treat the result as a pure calendar count, not as a business-day total. Public holidays, organization closures, leave, regional observances, and exceptional schedules are deliberately outside the calculation, because they require a jurisdiction and policy that are not present in the inputs. If those exclusions matter, use this count as the transparent baseline and subtract dates according to your own calendar. The explicit ISO date also helps pipelines that already carry a reporting date: callers do not need to split out or separately validate its year before requesting the count. Browser and API executions use the same pure solver, so identical inputs produce identical JSON. Automated API requests are priced at $0.002, while the deterministic structure makes results straightforward to cache by year and normalized weekday when repeated reporting workflows ask the same question.