Battlefield Wiki
Battlefield Wiki

This article is rated as standard
Overview Heroes BFV

"The VGO began life as an airplane-mounted machine gun. But it was soon adopted for land use. A high rate of fire made it a favorite among Allied commandos units."

— In-game description

The VGO is a weapon featured in Battlefield V. It was introduced tor the Support kit during the first week of Tides of War, Overture.

Unmodified, the weapon serves as an intermediate between the MG 34 and the MG 42 in terms of accuracy and controllability, primarily due to its fire rate of 830 RPM. Unlike the other MMGs however, the VGO is magazine-fed by default leading to quicker reloads, with the standard 60 round pan being slightly larger than the belt on its contemporaries. Per-shot recoil is towards the higher end of the MMG range. Accuracy when the bipod is undeployed is consistent in its weapon class, being generally poor, but its high fire rate can be useful against close range targets when firing from the hip is unavoidable. It is possible to overheat the VGO before its default magazine is exhausted through uninterrupted firing, as this occurs after a 51-round burst.

The specializations that the VGO has access to increase its control and general effectiveness. The left side of the tree has the Recoil Buffer, which reduces its vertical recoil to 0.975; Flashless Propellant, removing muzzle flash allowing greater precision and increasing obscurity at a distance; and Light Bolt boosts the fire rate from 830 RPM to 981 RPM. The right side of the tree improves reload speed by 15%, allowing one to go back into the fight quicker after each reload, especially with how fast one burns the ammo; Ported Barrel noticeably decreasing horizontal recoil; and Extended Magazine increasing the 60 round magazine to 100. The last two specializations are Incendiary Bullets, which increases its damage versus aircraft; and Chrome Lining, which increases the firing limit from 51 to 76 before overheating.



  • Due to a bug, the bipod on the VGO was not visible originally. This was fixed in the January 19th Update.