biztrac. BETA
COMPANY REGISTER PROFILE
998057531 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Wholesale of other machinery and equipment

VINGE MASKIN AS

Org. no. 998057531 Limited company (AS) Frosta Incorporated 2012 Active
Revenue 2025 NOK 12.6m
Operating profit NOK 44,000
Equity NOK 209,000
Incorporated 2012
Employees 7
Share capital NOK 400,000

VINGE MASKIN AS is registered as a limited company in Frosta, Trøndelag with organisation number 998057531. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2012 and has 7 registered employees. Registered share capital is NOK 400,000, divided into 1332 shares. The company's stated purpose is: “Kjøp og salg av anleggsmaskiner med tilhørende utstyr, vedlikehold av anleggsmaskiner og det som naturlig følger med slik virksomhet, samt delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.6m in revenue and NOK 44,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.6m
▼ −7 %
Operating profit
NOK 44,000
▲ +104 %
Equity
NOK 209,000
▼ −69 %
Est. value
NOK 2.3m

Financial health · 2025

Liquidity
0.94
Weak
Current assets ÷ current liabilities
Profitability
0.5%
Not satisfactory
Return on total assets
Solidity
1.8%
Not satisfactory
Equity as a share of total capital

Who owns VINGE MASKIN AS?

VINGE MASKIN AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about VINGE MASKIN AS

Who owns VINGE MASKIN AS?

Johannes Vinge is the largest registered owner, with 50.2%.

What is the revenue of VINGE MASKIN AS?

VINGE MASKIN AS had revenue of NOK 12.6m in 2025.

Who is the general manager of VINGE MASKIN AS?

Johannes Vinge is registered as general manager of VINGE MASKIN AS.

Where is VINGE MASKIN AS based?

VINGE MASKIN AS has its business address in Frosta.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.