-
John 6
- 1 厥後、耶穌渡加利利海、卽提比哩亞海、
- 2 從者甚衆、因見其行異蹟於病者也、
- 3 耶穌登山、偕其徒而坐、
- 4 猶太人之逾越節伊邇、
- 5 耶穌舉目、見就之者甚衆、語腓力曰、我儕何由市餅、以食斯衆乎、
- 6 言此、乃試之、蓋自知將何爲也、
- 7 腓力曰、以二十金之餅、使各得少許、亦不足也、
- 8 門徒之一、西門彼得之弟安得烈曰、
- 9 有童子攜麰麥餅五、小魚二、然於斯衆奚濟乎、
- 10 耶穌曰、令衆坐、其地多草、衆遂坐、數約五千、
- 11 於是耶穌取餅祝謝、分予坐者、魚亦然、如衆所願、
- 12 旣飽、耶穌謂其徒曰、拾其屑、勿使有遺、
- 13 遂拾五麰麥餅之屑、衆食而餘者、盈筐十二、
- 14 衆見其所行之異蹟、曰、是誠臨世之先知也、○
- 15 耶穌知衆將至、強之爲王、遂復退、獨入於山、○
- 16 及暮、其徒至海濱、
- 17 登舟欲濟、往迦百農、旣暝、耶穌尚未至、
- 18 風烈波揚、
- 19 門徒鼓櫂、約行十里有奇、見耶穌履海近舟、則懼、
- 20 耶穌曰、我也、勿懼、
- 21 門徒欣然接之登舟、而舟倏至所往之處、○
- 22 翌日、衆立彼岸、見有一艇、別無他舟、且見耶穌未偕其徒登舟、惟門徒獨往、
- 23 然有數艇來自提比哩亞、近主祝餅食衆之處、
- 24 衆見耶穌與其徒皆未在茲、遂登其艇、抵迦百農尋之、
- 25 遇於海之彼岸、則曰、夫子、何時至此、
- 26 耶穌曰、我誠語汝、爾尋我、非爲見異蹟、乃爲食餅而飽耳、
- 27 勿爲將壞之糧而勞、宜爲存至永生之糧而勞、卽人子將予爾者、蓋父上帝已印之矣、
- 28 衆曰、我儕當何爲以作上帝之工乎、
- 29 耶穌曰、信其所遣者、卽上帝之工也、
- 30 衆曰、爾行何異蹟、使我見而信爾乎、爾何所爲乎、
- 31 昔我祖食瑪那於野、記有之、主以自天之餅食之、
- 32 耶穌曰、我誠語汝、非摩西賜爾自天之餅、乃我父以自天之眞餅賜爾也、
- 33 蓋上帝之餅、乃降自天、以生賜世者也、
- 34 僉曰、主歟、常以斯餅賜我、
- 35 耶穌曰、我乃維生之餅、就我者必不飢、信我者永不渴、
- 36 然我曾語爾、爾見我而猶弗信也、
- 37 凡父予我者、必就我、就我者、我必不棄之、
- 38 蓋我降自天、非行己旨、乃行遣我者之旨、
- 39 凡所予我者、我弗失、而末日復起之、此遣我者之旨也、
- 40 凡見子而信之者、有永生、末日我將復起之、此我父之旨也、○
- 41 猶太人因耶穌言我乃自天而降之餅、遂訾議之、
- 42 曰、此非約瑟之子耶穌乎、其父母乃我所識者、今何言自天而降耶、
- 43 耶穌曰、毋相訾議也、
- 44 非遣我之父引之、無人能就我、就我者、我於末日復起之、
- 45 先知載云、衆將蒙上帝之訓焉、凡聽於父而學之者、則就我、
- 46 非謂有人見父、惟來自上帝者見之耳、
- 47 我誠語汝、信者有永生、
- 48 我乃維生之餅、
- 49 爾祖食瑪那於野、亦死焉、
- 50 食而不死者、天降之餅也、
- 51 我乃維生之餅、自天而降、人食之則永生、我所將予之餅、卽我之肉、爲世之生而予者也、○
- 52 猶太人遂爭論曰、斯人焉能以其肉食我乎、
- 53 耶穌曰、我誠語汝、非食人子之肉、而飲其血、則爾衷無生矣、
- 54 食我肉、飲我血者、有永生、我於末日復起之、
- 55 蓋我肉誠爲食、我血誠爲飲也、
- 56 食我肉、飲我血者、居我中、我亦居彼中焉、
- 57 維生之父遣我、我因父而生、食我者亦如是、因我而生、
- 58 此乃自天而降之餅、非如列祖食瑪那而死、食此餅者、必永生也、
- 59 此耶穌在迦百農會堂、訓誨而言也、○
- 60 其徒聞之、多云、難哉斯言、誰能聽之、
- 61 耶穌心知其徒緣此訾議、則曰、斯言躓爾耶、
- 62 設見人子升於故處、則何如、
- 63 畀生者神也、肉無益、我所語爾之言、神也、生也、
- 64 然爾中有弗信者矣、蓋耶穌自始卽知弗信者爲誰、賣己者爲誰也、
- 65 又曰、故我嘗語爾、非父予之、無人能就我也、○
- 66 由是其徒多退、不復從之、
- 67 耶穌謂十二徒曰、爾曹亦欲去乎、
- 68 西門彼得對曰、主有永生之道、吾誰與歸、
- 69 我儕已信、且知爾爲上帝之聖者、
- 70 耶穌曰、我非選爾十有二人乎、而爾中之一乃魔也、
- 71 言此、乃指加畧人西門之子猶大、十二徒之一、將賣耶穌者也、
-
-
King James Version (kjv)
- Afrikaans
- Albanian
- Arabic
- Armenian
- Basque
- Breton
- Calo
- Chamorro
- Cherokee
- Chinese
- Coptic
- Croatian
- Czech
- Danish
- Dari
- Dutch
-
English
American King James Version (akjv) American Standard Version (asv) Basic English Bible (basicenglish) Douay Rheims (douayrheims) John Wycliffe Bible (c.1395) (wycliffe) King James Version (kjv) King James Version (1769) with Strongs Numbers and Morphology and CatchWords, including Apocrypha (without glosses) (kjva) Webster's Bible (wb) Weymouth NT (weymouth) William Tyndale Bible (1525/1530) (tyndale) World English Bible (web) Young's Literal Translation (ylt)
- English and Klingon.
- Esperanto
- Estonian
- Finnish
- French
- German
- Gothic
- Greek
- Greek Modern
- Hebrew
- Hungarian
- Italian
- Japanese
- Korean
- Latin
- Latvian
- Lithuanian
- Malagasy
- Malayalam
- Manx Gaelic
- Maori
- Mongolian
- Myanmar Burmse
- Ndebele
- Norwegian bokmal
- Norwegian nynorsk
- Pohnpeian
- Polish
- Portuguese
- Potawatomi
- Romanian
- Russian
- Scottish Gaelic
- Serbian
- Shona
- Slavonic Elizabeth
- Spanish
- Swahili
- Swedish
- Syriac
- Tagalog
- Tausug
- Thai
- Tok Pisin
- Turkish
- Ukrainian
- Uma
- Vietnamese
-
-
Active Persistent Session:
To use a different persistent session key, simply add it above, and click the button below.
How This All Works
Your persistent session key, together with your favourite verse, authenticates you. It links to all your notes and tags in the Bible. You can share it with loved ones so they can see your notes and tags.
However, to modify your notes and tags, you need both the persistent session key and your favourite verse.
Please Keep Your Favourite Verse Private
Your persistent session key and favourite verse provide you exclusive access to edit your notes and tags. Think of your persistent session key as a username and your favourite verse as a password. Therefore, ensure your favourite verse is kept private.
The persistent session key allows viewing, while editing is only possible when the correct favourite verse is provided.
-
Loading...
-
Basic Hash Usage Explained
At getBible, we've established a robust system to keep our API synchronized with the Crosswire project's modules. Let me explain how this integration works in simple terms.
We source our Bible text directly from the Crosswire modules. To monitor any updates, we generate "hash values" for each chapter, book, and translation. These hash values serve as unique identifiers that change only when the underlying content changes, thereby ensuring a tight integration between getBible and the Crosswire modules.
Every month, an automated process runs for approximately three hours. During this window, we fetch the latest Bible text from the Crosswire modules. Subsequently, we compare the new hash values and the text with the previous ones. Any detected changes trigger updates to both our official getBible hash repository and the Bible API for all affected translations. This system has been operating seamlessly for several years.
Once the updates are complete, any application utilizing our Bible API should monitor the hash values at the chapter, book, or translation level. Spotting a change in these values indicates that they should update their respective systems.
Hash values can change due to various reasons, including textual corrections like adding omitted verses, rectifying spelling errors, or addressing any discrepancies flagged by the publishers maintaining the modules at Crosswire.
The Crosswire initiative, also known as the SWORD Project, is the "source of truth" for getBible. Any modifications in the Crosswire modules get reflected in our API within days, ensuring our users access the most precise and current Bible text. We pledge to uphold this standard as long as getBible exists and our build scripts remain operational.
We're united in our mission to preserve the integrity and authenticity of the Bible text. If you have questions or require additional information, please use our support system. We're here to assist and will respond promptly.
Thank you for your understanding and for being an integral part of the getBible community.
Favourite Verse
You should select one of your favourite verses.
This verse in combination with your session key will be used to authenticate you in the future.
This is currently the active session key.
Should you have another session key from a previous session.
You can add it here to load your previous session.