BIZTRAC BETA
Construction of residential and non-residential buildings

ST ENTREPRENØR AS

Org. no. 926678779 Limited company (AS) Voss Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 116.8m
Operating profit NOK 22.3m
Equity NOK 31.1m
Incorporated 2021
Employees 25
Share capital NOK 90,000

ST ENTREPRENØR AS is registered as a limited company in Voss, Vestland with organisation number 926678779. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021 and has 25 registered employees. Registered share capital is NOK 90,000, divided into 100 shares. The company's stated purpose is: “Bygg og anleggsarbeid og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 116.8m in revenue and NOK 22.3m in operating profit.

Key figures · 2025

Revenue
NOK 116.8m
Operating profit
NOK 22.3m
Equity
NOK 31.1m
Est. value
NOK 81.9m

Financial health · 2025

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

Who owns ST ENTREPRENØR AS?

NOVEDO ST HOLDING AS
ST ENTREPRENØR AS
NOK 116.8m rev. · NOK 22.3m profit

ST ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ST ENTREPRENØR AS

Who owns ST ENTREPRENØR AS?

NOVEDO ST HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ST ENTREPRENØR AS?

ST ENTREPRENØR AS had revenue of NOK 116.8m in 2025.

Who is the general manager of ST ENTREPRENØR AS?

Kristian Midthun Skjerven is registered as general manager of ST ENTREPRENØR AS.

Where is ST ENTREPRENØR AS based?

ST ENTREPRENØR AS has its business address in Voss.

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.