BIZTRAC BETA
Site preparation

VIK MASKIN AS

Org. no. 948955628 Limited company (AS) Frosta Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 538,000
Operating profit NOK −384,000
Equity NOK 1.8m
Incorporated 1988
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−384k kr).
  • Nylig endring 2026-02-06 Adresseendring registrert 2026-02-06.

VIK MASKIN AS is registered as a limited company in Frosta, Trøndelag with organisation number 948955628. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1988. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Maskingraving, sprenging, grøfting og transport.”. The most recent filed accounts, for the 2025 financial year, show NOK 538,000 in revenue and NOK −384,000 in operating profit.

Key figures · 2025

Revenue
NOK 538,000
Operating profit
NOK −384,000
Equity
NOK 1.8m
Est. value
NOK 865,000

Financial health · 2025

Liquidity
5.94
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
82.8%
Very good
Equity as a share of total capital

Who owns VIK MASKIN AS?

TORSTEIN VIK
VIK MASKIN AS
NOK 538,000 rev. · NOK −384,000 profit

VIK MASKIN AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VIK MASKIN AS own?

VIK MASKIN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about VIK MASKIN AS

Who owns VIK MASKIN AS?

TORSTEIN VIK is the largest registered owner, with 50.0%.

What is the revenue of VIK MASKIN AS?

VIK MASKIN AS had revenue of NOK 538,000 in 2025.

Who is the general manager of VIK MASKIN AS?

Torstein Vik is registered as general manager of VIK MASKIN AS.

Where is VIK MASKIN AS based?

VIK 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 15.06.2026.

Report a problem

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