ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Tiger Tanks in Combat in Hungary, 1944

Updated on February 13, 2011
The PzVI Tiger 2 tank
The PzVI Tiger 2 tank

October 22 Sunday

The 4th Panzer Corps attack and Operation Gypsybaron had stalled. A thick fog and mist forced the heavy Tigers of the 503rd Bn to only advance a few kilometers in the Törökszent-Miklós area. The Tiger tanks had also been aware of the Russian presence throughout the area. The Russian 7th Guards Army had counterattacked in part towards the northeast towards Tiszaföldvár and Torokszentmiklos with the 297th Division and 303rd Division near Mezotur. The 1st and 3rd Tiger Companies departed acting as a water break to meet the Russians in the local farms, which dotted the countryside. Each company sent five Tiger II tanks. However, observation was quite limited to 100 meters.

The Tigers of Company Three advanced slowly, each tank spaced 50 meters from the other. One of the tanks received a direct hit from a Rumanian 105mm artillery gun damaging the commander’s tank. Another Tiger gun fired sending the crew of the 105mm and the weapon to heaven. The Tigers continued to maneuver and the fog provided cover, however, some Tigers had been hit 24 times before pulling back into a safer position. Russian troops were amazed. The Tigers continued but now split, some moving towards Törökszent-Miklós. Tiger Company 2 had also finally arrived. The Germans continued to move northwards with the 24th Panzer Division elements as the 4th SS PG also merged some six km from Törökszent-Miklós. By some accounts, the area had 22 AT guns and four artillery guns. During the day, the Russians did infiltrate into the towns of Mezotur and Turkeve.

German units of the 1st Panzer Division were rather scattered about like seeds having been blown around by the wind. Its 37th SP Artillery battalion was near Hajdúnánás, its reconnaissance battalion at Hajdúdorog, its 113th PG Regiment near Újfehértó. Due to the thick armor, the Tigers seemed to be immune to anything Russians tossed at them, although, the intensity did manage to hinder their attack and response. In one case, three Russian AT guns fired at the Tiger with nearly no effect. A small wound from a metal splinter was received by one its occupants. Company Three of the 503rd Tiger battalion became involved in heavy combat in the Turkeve area with numerous tanks from the Russian 18th Tank Corps. T34 tanks fired and tried to fire at the tigers from the side, where weaker armor was located. It also made for an easier target. The Russian tankers would always try this tactic and then fire at the tiger tanks wheel and tracks, which were unprotected. Disabling a tiger made it much easier to achieve a kill.

The Russian Pliyev Group had captured Nyíregyháza, and by doing so, had cutoff 150,000 men of the German 8th Army! The question was, like the Germans who had cut off the same corps’ earlier, could Pliyev actually continue to bag the Germans? It was a dilemma the Germans could not afford to lose. They had already lost the 6th Army and 150,000 men at Stalingrad in 1942. It deja vu once again.

Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)