Occurs close inshore and offshore down to at least 100 m depth. Presumably feeds on small fishes, cephalopods and crustaceans. Ovoviviparous, with 8 to 22 young in a litter. Size at birth about 20 to 21 cm. Utilized for human consumption.
Physical description for Japanese topeshark is currently being compiled.
Behavioural data for Japanese topeshark is currently being reviewed.
Diet information for Japanese topeshark is currently being compiled.
Ovoviviparous, embryos feed solely on yolk .
Marine; demersal; depth range 20 - 345 m . Subtropical; 40°N - 19°N, 112°E - 141°E Northwest Pacific: China, Taiwan, Korea, and Japan.
small fishes, cephalopods and crustaceans
"Japanese topeshark is an edible species."
Detailed nutritional data for Japanese topeshark is currently being compiled from USDA FoodData Central.
Mercury data for Japanese topeshark has not yet been assigned. Please consult FDA/EPA guidance for general seafood safety advice.
| Language | Common Names |
|---|---|
| 🇬🇧English | Japanese topeshark |
| 🌍CES | psohlav japonský |
| 🇩🇪German | Japanischer Hundshai |
| 🇫🇮Finnish | japaninkoirahai |
| 🇫🇷French | Requin-há Dochizame |
| 🇯🇵Japanese | Eirakubuka · エイラクブカ |
| 🇳🇱Dutch | Japanse vaalhaai |
| 🇵🇹Portuguese | Tubarão-focinho-liso |
| 🇷🇺Russian | Японская суповая акула |
| 🇪🇸Spanish | Cazón Japonés |
| 🇨🇳Chinese | 日本半皺唇鯊 · 日本半皺唇鯊(日本翅鯊 · 日本灰鮫 · 日本翅沙 · 日本翅鯊 · 沙條 · 白鯊仔 · 胎沙 · 赤匏仔 |
| Scientific Name | Author | Year | Status |
|---|---|---|---|
| ? japonica | Müller & Henle | 1839 | Synonym |
| Galeorhinus japonicus | Müller & Henle | 1839 | Synonym |
| Galeus japanicus | Müller & Henle | 1839 | Synonym |
| Hemitriakis japonica | Müller & Henle | 1839 | Synonym |
Occurrence records from the Global Biodiversity Information Facility (GBIF) - 2 records indexed .
No observations yet - be the first to log one!
View all observations for Japanese topeshark ↗Spotted incorrect or outdated data? Submit a correction and our editorial team will review it. Approved edits go live within 48 hours.
Found a factual error, broken data, or inappropriate content? Let us know and we will investigate promptly.