PB-9867 / Jōyō reference
顧.
Look Back in Japanese
かえりみるkaerimiru
Look Back.
顧 (kaerimiru) is a kanji glossed as “Look Back”. Recorded details: on’yomi コ; kun’yomi かえりみる; 21 strokes.
Look inside顧 / LOOK BACK
01 / WHAT YOU CAN SEE
Look closely at the form.
This page begins with the present written form 顧; structural and historical interpretation remain separate.
04 / WORDS YOU STILL HEAR
Words in everyday Japanese.
- 顧問
- こもんadviser, advisor
- 顧客
- こきゃくcustomer, client
- 回顧
- かいこrecollecting, reminiscing
CHARACTER REFERENCE
A calm first reference.
Dictionary facts, visible structure and historical interpretation are kept distinct.
- Kanji
- 顧
- Primary meaning
- Look Back
- Onyomi
- コ
- Kunyomi
- かえりみる
- Stroke count
- 21
- Radical
- 頁
- Components
- —
STRUCTURAL EXPLANATION
This page begins with the present written form 顧; structural and historical interpretation remain separate.
COMMON VOCABULARY
- 顧問
- こもんadviser, advisor
- 顧客
- こきゃくcustomer, client
- 回顧
- かいこrecollecting, reminiscing
RELATED KANJI
Explore this character in the Graph Explorer.
SIMILAR KANJI
No close visual match listed.
Reading and usage entries come from cited dictionary material. Structural observations describe the written form. Historical accounts remain attributed interpretations, not settled fact.
FOLLOW THE CONNECTION
Where do you want to go next?
A PATH FROM HERE
CONTINUE EXPLORING
No published relationship starts here yet. Open the verified map to inspect the current graph state.
SEE THIS CHARACTER IN THE MAPBROWSE ONLY
Keep moving through the collection.
These next cards are navigation aids, not verified relationships.
A LIVING CONNECTION
SEE IN THE GRAPHOpen the verified map to find this character’s recorded connections.
SOURCES & EDITORIAL NOTES
- KANJIDIC2 · 顧 ↗
identity=顧;on=コ;kun=かえりみる;strokeCount=21;classicalRadical=181;meaning=look back
- JMdict · 顧 ↗
顧問=こもん (JMdict ent_seq 1267880); 顧客=こきゃく (JMdict ent_seq 1578540); 回顧=かいこ (JMdict ent_seq 1199440)
English explanations are editorial paraphrases. Visual observations, dictionary history and current usage are identified separately.
