Kanji Pair Research
Enter one kanji to discover other characters recorded in the same JMnedict name spellings, or enter two kanji to inspect that exact co-occurrence. Every count in this research view describes the imported corpus—not population popularity in Japan.
longevity, congratulations, one's natural life
Characters recorded with 寿
Only partners appearing in at least two distinct source-recorded written forms are highlighted here. That threshold keeps one-off combinations from looking more established than the corpus supports.
寿 + 美
103 distinct written forms · 132 source rows
53 given-name readings · 0 surname readings寿 + 子
103 distinct written forms · 129 source rows
36 given-name readings · 0 surname readings寿 + 実
53 distinct written forms · 59 source rows
31 given-name readings · 0 surname readings寿 + 々
36 distinct written forms · 37 source rows
18 given-name readings · 0 surname readings寿 + 恵
35 distinct written forms · 43 source rows
23 given-name readings · 0 surname readings寿 + 亜
30 distinct written forms · 32 source rows
12 given-name readings · 0 surname readings寿 + 香
29 distinct written forms · 35 source rows
19 given-name readings · 0 surname readings寿 + 加
28 distinct written forms · 33 source rows
18 given-name readings · 0 surname readings寿 + 佳
24 distinct written forms · 30 source rows
22 given-name readings · 0 surname readings寿 + 江
24 distinct written forms · 30 source rows
15 given-name readings · 0 surname readings寿 + 代
22 distinct written forms · 25 source rows
9 given-name readings · 0 surname readings寿 + 奈
20 distinct written forms · 24 source rows
14 given-name readings · 0 surname readings寿 + 志
20 distinct written forms · 22 source rows
13 given-name readings · 0 surname readings寿 + 安
19 distinct written forms · 23 source rows
11 given-name readings · 0 surname readings寿 + 万
18 distinct written forms · 21 source rows
16 given-name readings · 0 surname readings寿 + 三
18 distinct written forms · 21 source rows
17 given-name readings · 0 surname readings寿 + 枝
17 distinct written forms · 21 source rows
13 given-name readings · 0 surname readings寿 + 男
17 distinct written forms · 20 source rows
11 given-name readings · 0 surname readings寿 + 満
17 distinct written forms · 19 source rows
15 given-name readings · 0 surname readings寿 + 里
17 distinct written forms · 19 source rows
14 given-name readings · 0 surname readings寿 + 嘉
16 distinct written forms · 20 source rows
14 given-name readings · 0 surname readings寿 + 弥
16 distinct written forms · 20 source rows
15 given-name readings · 0 surname readings寿 + 穂
16 distinct written forms · 17 source rows
12 given-name readings · 0 surname readings寿 + 雄
15 distinct written forms · 18 source rows
13 given-name readings · 0 surname readings寿 + 久
15 distinct written forms · 17 source rows
13 given-name readings · 0 surname readings寿 + 郎
14 distinct written forms · 28 source rows
24 given-name readings · 0 surname readings寿 + 千
14 distinct written forms · 23 source rows
15 given-name readings · 0 surname readings寿 + 花
14 distinct written forms · 15 source rows
10 given-name readings · 0 surname readings寿 + 華
14 distinct written forms · 15 source rows
10 given-name readings · 0 surname readings寿 + 真
12 distinct written forms · 16 source rows
13 given-name readings · 0 surname readings寿 + 阿
12 distinct written forms · 12 source rows
4 given-name readings · 0 surname readings寿 + 須
12 distinct written forms · 12 source rows
5 given-name readings · 0 surname readings寿 + 梨
11 distinct written forms · 11 source rows
9 given-name readings · 0 surname readings寿 + 賀
11 distinct written forms · 11 source rows
11 given-name readings · 0 surname readings寿 + 夫
10 distinct written forms · 15 source rows
12 given-name readings · 0 surname readings寿 + 愛
10 distinct written forms · 13 source rows
10 given-name readings · 0 surname readingsCo-occurrence is not popularity or etymology
The pair relation comes from exact JMnedict source rows through the compact kanji-usage index. KANJIDIC2 contributes character metadata only. A high corpus count can reflect dictionary coverage and should not be read as a national usage frequency.