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

STAVRUM AS

Org. no. 915680836 Limited company (AS) Stjørdal Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 668,000
Equity NOK 2.4m
Incorporated 2015
Share capital NOK 30,000

STAVRUM AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 915680836. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Byggtjenester, murarbeid, betongarbeid, kjerneboring, utleie av personell g utstyr, samt andre produkter som naturlig faller sammen med dette. Herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 668,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 668,000
Equity
NOK 2.4m
Est. value
NOK 3.3m

Financial health · 2024

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

Who owns STAVRUM AS?

JØRGEN BERDAL STAVRUM
STAVRUM AS
NOK 3.3m rev. · NOK 668,000 profit

STAVRUM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STAVRUM AS

Who owns STAVRUM AS?

JØRGEN BERDAL STAVRUM is the largest registered owner, with 100.0%.

What is the revenue of STAVRUM AS?

STAVRUM AS had revenue of NOK 3.3m in 2025.

Who is the general manager of STAVRUM AS?

Jørgen Berdal Stavrum is registered as general manager of STAVRUM AS.

Where is STAVRUM AS based?

STAVRUM AS has its business address in Hell.

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.