<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Comparing Peco Track With Hornby Track	</title>
	<atom:link href="https://blog.model-train-help.com/2020/12/comparing-peco-track-hornby-track.html/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.model-train-help.com/2020/12/comparing-peco-track-hornby-track.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=comparing-peco-track-hornby-track</link>
	<description>Model railroads and model trains</description>
	<lastBuildDate>Wed, 30 Dec 2020 06:31:15 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Hervey		</title>
		<link>https://blog.model-train-help.com/2020/12/comparing-peco-track-hornby-track.html#comment-42968</link>

		<dc:creator><![CDATA[Hervey]]></dc:creator>
		<pubDate>Wed, 30 Dec 2020 06:31:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.model-train-help.com/?p=5931#comment-42968</guid>

					<description><![CDATA[Peco is viewed as a better quality of track specially in the turn outs. You will probably have fewer headaches if you go with Peco and if you are careful with the setup they should last a very longtime. What ever you decide to do don&#039;t mix and match. Doing so introduces variation and that is a recipe for trouble in the form of derailments. Even if they are the same gauge the rail height and shape will not be identical for the same code, hence variability.]]></description>
			<content:encoded><![CDATA[<p>Peco is viewed as a better quality of track specially in the turn outs. You will probably have fewer headaches if you go with Peco and if you are careful with the setup they should last a very longtime. What ever you decide to do don&#8217;t mix and match. Doing so introduces variation and that is a recipe for trouble in the form of derailments. Even if they are the same gauge the rail height and shape will not be identical for the same code, hence variability.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Bruce		</title>
		<link>https://blog.model-train-help.com/2020/12/comparing-peco-track-hornby-track.html#comment-42965</link>

		<dc:creator><![CDATA[Bruce]]></dc:creator>
		<pubDate>Wed, 30 Dec 2020 06:03:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.model-train-help.com/?p=5931#comment-42965</guid>

					<description><![CDATA[Having purchased and used Hornby track exclusively and experienced running on Peco I personally would recommend Peco. 

All Hornby points (Turnouts/Switches) have insulated frogs (Peco have both, insulated frogs and non-insulated Frogs). Hornby&#039;s insulated sections are so large that sometimes even my 0-6-0 will cut-out where as on the Peco Insu-Frog this does not happen.
In addition, Peco offer  several styles of rails (Set Track which is the equivalent to Hornby), Code 100, Code 75 just to name a couple. They also have the &quot;old&quot; wooden sleeper (tie) or the newer concrete sleeper style. It depends on the location and era you intend to model.]]></description>
			<content:encoded><![CDATA[<p>Having purchased and used Hornby track exclusively and experienced running on Peco I personally would recommend Peco. </p>
<p>All Hornby points (Turnouts/Switches) have insulated frogs (Peco have both, insulated frogs and non-insulated Frogs). Hornby&#8217;s insulated sections are so large that sometimes even my 0-6-0 will cut-out where as on the Peco Insu-Frog this does not happen.<br />
In addition, Peco offer  several styles of rails (Set Track which is the equivalent to Hornby), Code 100, Code 75 just to name a couple. They also have the &#8220;old&#8221; wooden sleeper (tie) or the newer concrete sleeper style. It depends on the location and era you intend to model.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
