Japan earthquakes, down to the local station
EN
Open interactive map
MenuMore
JMA EPICENTRE REGION

Adjacent Sado

佐渡付近

earthquakes94
Maximum M6
Maximum Shindo5−
FirstFeb 20, 2015

What this epicentre-region name means

This page groups earthquakes whose JMA report uses this epicentre-region name. It identifies the reported epicentre region, not the area where shaking was felt or an administrative boundary.

JISHINDESU stores 94 confirmed or corrected reports from Feb 20, 2015 to Nov 15, 2025. This is not JMA’s complete historical earthquake catalogue. Dates and times use Japan Standard Time (JST).

Earthquakes in the stored history

The largest magnitude and highest Shindo may belong to different earthquakes. Open each report for its details.

Stored reports by year

The largest number of stored reports is 70 in 2024. Yearly counts describe the stored reports, not future activity or relative hazard.

  1. 20255
  2. 202470
  3. 20232
  4. 20221
  5. 20213
  6. 20201
  7. 20194
  8. 20181
  9. 20171
  10. 20164
  11. 20152

Prefectures with observations

Each count is the number of earthquakes with a Shindo reading at a station in that prefecture. It does not locate the epicentre or imply shaking throughout the prefecture. One earthquake may appear in several prefectures.

NiigataEarthquakes observed: 75 · Highest local Shindo: 5−IshikawaEarthquakes observed: 63 · Highest local Shindo: 4ToyamaEarthquakes observed: 21 · Highest local Shindo: 3NaganoEarthquakes observed: 8 · Highest local Shindo: 3FukushimaEarthquakes observed: 8 · Highest local Shindo: 3FukuiEarthquakes observed: 8 · Highest local Shindo: 2YamagataEarthquakes observed: 7 · Highest local Shindo: 3GifuEarthquakes observed: 6 · Highest local Shindo: 2GunmaEarthquakes observed: 5 · Highest local Shindo: 2TochigiEarthquakes observed: 3 · Highest local Shindo: 2AkitaEarthquakes observed: 1 · Highest local Shindo: 2SaitamaEarthquakes observed: 1 · Highest local Shindo: 2

Recent earthquakes

Showing the latest 50 of 94 stored reports, not the complete list.

2Adjacent SadoNov 15, 2025, 22:03 JST · M4.1View report →1Adjacent SadoJul 22, 2025, 04:05 JST · M3.9View report →1Adjacent SadoJul 1, 2025, 18:46 JST · M4.1View report →2Adjacent SadoApr 4, 2025, 19:46 JST · M3.2View report →2Adjacent SadoFeb 10, 2025, 14:12 JST · M3.7View report →1Adjacent SadoDec 2, 2024, 08:39 JST · M4.1View report →1Adjacent SadoNov 3, 2024, 18:58 JST · M3.7View report →1Adjacent SadoAug 27, 2024, 17:13 JST · M3.9View report →1Adjacent SadoJul 1, 2024, 12:32 JST · M4.2View report →1Adjacent SadoJun 8, 2024, 08:08 JST · M3.7View report →1Adjacent SadoApr 28, 2024, 18:28 JST · M4View report →1Adjacent SadoMar 5, 2024, 11:17 JST · M4.1View report →3Adjacent SadoFeb 15, 2024, 12:48 JST · M5.1View report →2Adjacent SadoFeb 11, 2024, 18:35 JST · M4.2View report →4Adjacent SadoFeb 7, 2024, 06:08 JST · M5.1View report →1Adjacent SadoFeb 1, 2024, 14:10 JST · M4View report →1Adjacent SadoJan 30, 2024, 10:49 JST · M3.8View report →1Adjacent SadoJan 30, 2024, 09:22 JST · M3.7View report →1Adjacent SadoJan 29, 2024, 16:27 JST · M4View report →1Adjacent SadoJan 29, 2024, 07:59 JST · M3.7View report →2Adjacent SadoJan 19, 2024, 22:06 JST · M4.2View report →2Adjacent SadoJan 19, 2024, 20:22 JST · M4.3View report →1Adjacent SadoJan 18, 2024, 10:51 JST · M4.1View report →1Adjacent SadoJan 13, 2024, 09:21 JST · M4View report →1Adjacent SadoJan 11, 2024, 12:21 JST · M3.5View report →1Adjacent SadoJan 11, 2024, 04:32 JST · M4.1View report →1Adjacent SadoJan 10, 2024, 20:02 JST · M4View report →1Adjacent SadoJan 10, 2024, 09:16 JST · M3.6View report →1Adjacent SadoJan 10, 2024, 08:54 JST · M4View report →1Adjacent SadoJan 10, 2024, 02:41 JST · M3.5View report →2Adjacent SadoJan 9, 2024, 20:10 JST · M4.2View report →1Adjacent SadoJan 9, 2024, 19:10 JST · M3.9View report →2Adjacent SadoJan 9, 2024, 18:55 JST · M4.4View report →1Adjacent SadoJan 9, 2024, 18:09 JST · M3.9View report →5−Adjacent SadoJan 9, 2024, 17:59 JST · M6View report →1Adjacent SadoJan 8, 2024, 18:35 JST · M3.5View report →1Adjacent SadoJan 6, 2024, 14:30 JST · M3.5View report →1Adjacent SadoJan 6, 2024, 13:00 JST · M3.5View report →1Adjacent SadoJan 6, 2024, 05:43 JST · M4.1View report →1Adjacent SadoJan 6, 2024, 01:38 JST · M4.1View report →1Adjacent SadoJan 5, 2024, 10:56 JST · M3.9View report →1Adjacent SadoJan 4, 2024, 23:08 JST · M3.9View report →2Adjacent SadoJan 4, 2024, 21:30 JST · M4.1View report →3Adjacent SadoJan 4, 2024, 17:16 JST · M5View report →2Adjacent SadoJan 4, 2024, 04:38 JST · M4.9View report →1Adjacent SadoJan 3, 2024, 22:09 JST · M4View report →2Adjacent SadoJan 3, 2024, 20:45 JST · M3.2View report →1Adjacent SadoJan 3, 2024, 17:15 JST · M4View report →1Adjacent SadoJan 3, 2024, 13:04 JST · M4.1View report →1Adjacent SadoJan 3, 2024, 12:48 JST · M4.1View report →