Thank you for correcting the text in this article. Your corrections improve Papers Past searches for everyone. See the latest corrections.

This article contains searchable text which was automatically generated and may contain errors. Join the community and correct any errors you spot to help us improve Papers Past.

Article image
Article image
Article image
Article image
Article image
Article image

THE WAR.

IN MANCHURIA.

KURCPATKIN'S CHEERLESS REPORT. JAPANESE OCCUPY HAICHENG. fPRBSS ASSOCIATION.] (Received August 4, 7.40 a.m.) LONDON, August 3. General Kuropatkin reports the results of the Yangtzufing fight as' a retirement after stubborn resistance from the advanced posts to their principal position. General Kuropatkin hopes that in the main position they will successfully struggle, even against superior numbers. Reports from Niuchwang state) that the Japanese have occupied Haicheng. RUSSIAN ARMY RETIRING. (Received August 4, 8.48 a.m.) LONDON. August 3. General Kuropatkin's army is retiriug via Aushantian. The Japanese, casualties at Tumuchan are estimated at 400< RUSSO-CHINESB BANK. ! LONDON, August 3.' It is expected at Niuchwang that the. Japanese will seize the Russo-Chinese Bank ; funds, because it represents the Russian Government's property. ifee Japanese flag is floating over the, bank. NEWS FROM KUROKI. CONTINUED JAPANESE SUCCESS. (Received August 3, V 11.36V 11.36 p.m.) LONDON, August 3. General Kuroki reports that he is attacking two divisions of. Russians at Kushulientze, four miles west of Haihfyen , (? Haicheng), two divisions and a half at i Yang-tze-ling, and six west of Motienling. i. Both armies reached 25 miles west of Liaoyang. At sunset on Sunday both Russian wings [ at Kushulientze were defeated, but owing ) to their large force and strong positions ■ the fact was not disclosed till noon on Monday. The victors pursued tho Rus- ; sians, who fled to Auming. The prin- > cipal positions at Yang-tze-ling were car- \, ried at sunset, but a portion of the; enemy 3 stubbornly, resisted. The attack was rc3 sumed on Monday, and the height cap- . tured, the Russians fleeing to Tanghoyan. i Some field pieces were captured. - CAPTURE OF SIMUCHENG. j . 1 (Received August 4, 7.56 a.m.) 1 LONDON, August 3. a The Temps' correspondent at Haicheng s reports that two divisions with 60 guns on c Sunday attacked Simucheng, which the i Russians evacuated the following evening - under the enemy's heavy artillery fire. ] The Japanese forces consisted' of seven divisions, including a large proportion oi -• fresh troops and many guns. i BATTLE NEAR HAICHENG. B RUSSIANS LOSE HEAVILY. 0 • ■ "■ (Received August &, 8.10 a.m.) 1 LONDON, August 3. c The Japanese carried an entrenched I position at Toiauchah, 15 miles south-east 8 of Kaicheng, on Saturday and Sunday. The Russians, who left 1500 dead and c lost six guns, 'retired to Haicheng. > General Kuropatkin since reports having evacuated Haicheng. c It is officially reported that the Japanese casualties at Yang-tze-leng and Kai shulutza were 950. - RUSSIAN TROOPS SUFFERING FROfe HUNGER. Italian papers describe the Russians ir the Liaoyang district as suffering terrible j hunger. After 46 hours' fighting /the of 6 ficers only received small rations of sugar

Permanent link to this item

https://paperspast.natlib.govt.nz/newspapers/HNS19040804.2.12

Bibliographic details

Hawera & Normanby Star, Volume XLVIII, Issue 8052, 4 August 1904, Page 2

Word Count
440

THE WAR. IN MANCHURIA. Hawera & Normanby Star, Volume XLVIII, Issue 8052, 4 August 1904, Page 2

THE WAR. IN MANCHURIA. Hawera & Normanby Star, Volume XLVIII, Issue 8052, 4 August 1904, Page 2

Help

Log in or create a Papers Past website account

Use your Papers Past website account to correct newspaper text.

By creating and using this account you agree to our terms of use.

Log in with RealMe®

If you’ve used a RealMe login somewhere else, you can use it here too. If you don’t already have a username and password, just click Log in and you can choose to create one.


Log in again to continue your work

Your session has expired.

Log in again with RealMe®


Alert