USS Refresh
1944 Admirable-class minesweeper

USS Refresh (hull number AM-287) was an Admirable-class minesweeper built for the U.S. Navy during World War II. She was built to clear minefields in offshore waters, and served the Navy in the Pacific Ocean. Post-war, her crew returned home with two battle stars to their credit.
The ship itself was given to the Republic of China Navy in June 1948, initially renamed ROCS Yung Chang (AM-51), and sometime later renamed Lin Huai. Following 17 years of service with its second navy, Lin Huai was hit by a PLA Navy torpedo and sunk during the Battle of East Chongwu in November 1965.
Career
Refresh, a minesweeper, was laid down 22 September 1943 by the General Engineering & Dry Dock Company, of Alameda, California, launched 12 April 1944, sponsored by Miss Muriel Maddox of San Francisco, California; and, commissioned 10 April 1945.
Following a Pacific coast shakedown out of San Pedro, California, Refresh reported to Commander in Chief, Pacific for duty 9 June 1945. After a call at Pearl Harbor, she departed 1 July for Okinawa via Eniwetok and Guam. Arriving Buckner Bay 31 July, she joined Commander, Mine Squadron 15 and began minesweeping operations in the Okinawa area 13 August. The last week of August she swept the approaches to Jinsen, Korea, and operated in the Yellow Sea through 7 September.
During the remainder of September, Refresh assisted task group TG 52.3 in minesweeping operations in the East China Sea approaches to Nagasaki and Sasebo, Japan, and in the Goto Archipelago, primarily in the area of Fukse, southwest of Kyūshū.
“USS Refresh” enters the record as 1944 Admirable-class minesweeper. Crown Archives preserves that source wording while asking what Refresh, Admirable-class and minesweeper can confirm, complicate or overturn.
Why this record matters
“USS Refresh” is worth following because a concise public description often conceals a longer documentary argument. Here, Refresh, Admirable-class and minesweeper provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jul 11, 2026. The linked authority identifier is Q9364184. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1948, 1965, 1943 and 1944.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “USS Refresh”, its source revision and the description used here.
- Expand the search: follow USS Refresh primary sources, USS Refresh archive and Refresh research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “USS Refresh”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “USS Refresh” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.