Earthquake record › Nevada

Nevada in the Sealed USGS Record

259 events whose USGS place string ends in Nevada, across 62 of our daily seals. Counts are of what we sealed, not of what occurred.

What this archive is, exactly. The USGS all_day feed holds the last 24 hours and is overwritten in place. We seal one dated copy of it per day. An event that appeared in the feed and was superseded between two of our seals is not in this archive at all. These pages are a record of what USGS asserted at each seal — they are not a complete catalogue of earthquakes, and nothing here should be read as one.

Review status as sealed: automatic 154, reviewed 105. An automatic value is a machine solution USGS may still revise; a reviewed value has had a human look at it. Which one you are reading matters more than the magnitude itself.

By magnitude

Magnitude	Events
Below M1.0	0
M1.0 – M1.9	172
M2.0 – M2.9	78
M3.0 – M3.9	9
M4.0 – M4.9	0
M5.0 and above	0
No magnitude published	0

2 of 259 events in Nevada were sealed at or above M3.5 — the magnitude Texas Railroad Commission seismic-response conditions are written around. That is a count of what the feed said, not a determination about any permit, operator or well.

Get told when the record changes for Nevada

USGS publishes the last day and overwrites it, then revises events in place — automatic becomes reviewed, magnitudes move, and the old value stops existing everywhere. We seal a dated copy every day. Leave your email and we'll tell you when an event in Nevada is revised after the fact, with what it said before.

Email me revisions for Nevada →

Work email only. No newsletter, no obligation.

Prefer to just buy it? See the custom, source-cited close file, priced, with a sample deliverable.

Narrower views

M1.0 – M1.9 172
M2.0 – M2.9 78

Present but below our page threshold, so named here instead of given a page: M3.0 – M3.9 (9).

Largest events on record here

Magnitude	Place, as published	Review status	Seal
M3.64	45 km SE of Beatty, Nevada	reviewed	2026-07-18
M3.50	16 km NE of Yerington, Nevada	reviewed	2026-07-23
M3.45	18 km NNW of Indian Springs, Nevada	reviewed	2026-06-26
M3.40	18 km SE of Silver Springs, Nevada	reviewed	2026-07-28
M3.39	47 km SE of Beatty, Nevada	reviewed	2026-07-09
M3.24	22 km NNE of Yerington, Nevada	reviewed	2026-08-05
M3.10	76 km SSE of Lamoille, Nevada	reviewed	2026-07-05
M3.03	54 km ESE of Goldfield, Nevada	reviewed	2026-07-12
M3.01	76 km ENE of Tonopah, Nevada	reviewed	2026-08-19
M2.99	46 km ESE of Beatty, Nevada	reviewed	2026-07-09
M2.99	17 km NNW of Indian Springs, Nevada	reviewed	2026-07-12
M2.96	17 km SE of Silver Springs, Nevada	reviewed	2026-07-28
M2.93	35 km WNW of Indian Springs, Nevada	automatic	2026-08-09
M2.90	20 km ESE of Silver Springs, Nevada	automatic	2026-07-13
M2.85	75 km ENE of Tonopah, Nevada	reviewed	2026-08-19
M2.79	19 km SSW of Silver Peak, Nevada	automatic	2026-08-05
M2.79	78 km S of Eureka, Nevada	reviewed	2026-08-07
M2.78	18 km SE of Silver Springs, Nevada	reviewed	2026-07-21
M2.77	75 km ENE of Tonopah, Nevada	reviewed	2026-08-19
M2.71	35 km SE of Alamo, Nevada	automatic	2026-07-31

How this page decides a place is in Nevada. USGS writes the region after the last comma of the place string, and we map that tail from an explicit table — we never geocode the coordinates. An event just offshore or just over a border is assigned the way USGS wrote it, and an event whose place string carries no comma is never assigned here at all. The complete table is on the methodology page.

Days we did not seal. 69 seals span 77 calendar days, so these days inside the span have no sealed copy: 2026-07-04, 2026-07-15, 2026-08-14, 2026-08-15, 2026-08-16, 2026-08-17, 2026-08-22, 2026-08-23. A missing day means we did not read the feed. It does not mean nothing happened, and those dates return a 404 here rather than a page reading zero.

One seal is wider than the others. These dates were collected more than once: 2026-07-16 (2 runs, 00:48 and 13:42 UTC), 2026-08-18 (2 runs, 05:41 and 23:15 UTC), 2026-08-24 (12 runs, 00:43 and 11:00 UTC), 2026-08-25 (11 runs, 02:00 and 22:09 UTC), 2026-08-26 (4 runs, 00:05 and 22:05 UTC), 2026-08-27 (4 runs, 00:05 and 22:09 UTC), 2026-08-28 (4 runs, 00:05 and 22:08 UTC), 2026-08-29 (4 runs, 00:08 and 22:05 UTC), 2026-08-30 (4 runs, 00:07 and 22:05 UTC), 2026-08-31 (4 runs, 00:05 and 22:08 UTC), 2026-09-01 (4 runs, 00:06 and 22:10 UTC), 2026-09-02 (4 runs, 00:05 and 22:05 UTC), 2026-09-03 (4 runs, 00:09 and 22:09 UTC), 2026-09-04 (4 runs, 00:07 and 22:08 UTC), 2026-09-05 (4 runs, 00:08 and 22:06 UTC), 2026-09-06 (4 runs, 00:09 and 22:08 UTC), 2026-09-07 (4 runs, 00:09 and 22:05 UTC). A day with two runs covers more than 24 source-hours, so its event count is larger for a collection reason and not a seismic one. Do not read it as a busy day.

Compiled from dated copies of the U.S. Geological Survey's public all_day realtime feed (a work of the US government, in the public domain). Values are reproduced exactly as USGS published them on the date shown and may since have been revised; USGS is the authority on the current value of any event. These pages are provided for informational purposes only, carry no warranty of accuracy or completeness, and are not an earthquake warning, a safety notice, or engineering advice. Always verify against the USGS Earthquake Hazards Program before relying on any figure.

Earthquake record home · What the record changed · How this is collected · US Tech Automations.