BIZTRAC BETA
Other specialised construction activities n.e.c.

STOKKEBØ MASKIN AS

Org. no. 998551110 Limited company (AS) Vik Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 16.2m
Operating profit NOK 1.1m
Equity NOK 6.5m
Incorporated 2012
Employees 7
Share capital NOK 210,000

Signals

1 flags
  • Nylig endring 2026-02-02 Adresseendring registrert 2026-02-02.

STOKKEBØ MASKIN AS is registered as a limited company in Vik, Vestland with organisation number 998551110. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2012 and has 7 registered employees. Registered share capital is NOK 210,000, divided into 210 shares. The company's stated purpose is: “Spesialisert bygge- og anleggsvirksomhet og anna verksemd som har samanheng med dette”. The most recent filed accounts, for the 2024 financial year, show NOK 16.2m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 16.2m
Operating profit
NOK 1.1m
Equity
NOK 6.5m
Est. value
NOK 6.4m

Financial health · 2024

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

Who owns STOKKEBØ MASKIN AS?

ERLING STOKKEBØ
STOKKEBØ MASKIN AS
NOK 16.2m rev. · NOK 1.1m profit

STOKKEBØ MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STOKKEBØ MASKIN AS

Who owns STOKKEBØ MASKIN AS?

ERLING STOKKEBØ is the largest registered owner, with 50.5%.

What is the revenue of STOKKEBØ MASKIN AS?

STOKKEBØ MASKIN AS had revenue of NOK 16.2m in 2024.

Who is the general manager of STOKKEBØ MASKIN AS?

Erling Stokkebø is registered as general manager of STOKKEBØ MASKIN AS.

Where is STOKKEBØ MASKIN AS based?

STOKKEBØ MASKIN AS has its business address in Vangsnes.

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.