BIZTRAC BETA
Construction of residential and non-residential buildings

SUBMET ENTREPRENØR AS

Org. no. 922114137 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 42.3m
Operating profit NOK −6.7m
Equity NOK 90,000
Incorporated 2018
Employees 73
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6,7 mill kr).

SUBMET ENTREPRENØR AS is registered as a limited company in Oslo, Oslo with organisation number 922114137. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018 and has 73 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet, med særlig spesialisering innen betongarbeid og tømrerarbeid som underentreprenør.”. The most recent filed accounts, for the 2024 financial year, show NOK 42.3m in revenue and NOK −6.7m in operating profit.

Key figures · 2024

Revenue
NOK 42.3m
Operating profit
NOK −6.7m
Equity
NOK 90,000
Est. value
NOK 14.8m

Financial health · 2024

Liquidity
0.76
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SUBMET ENTREPRENØR AS?

SUBMET INVEST AS
SUBMET ENTREPRENØR AS
NOK 42.3m rev. · NOK −6.7m profit

SUBMET ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SUBMET ENTREPRENØR AS

Who owns SUBMET ENTREPRENØR AS?

SUBMET INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of SUBMET ENTREPRENØR AS?

SUBMET ENTREPRENØR AS had revenue of NOK 42.3m in 2024.

Where is SUBMET ENTREPRENØR AS based?

SUBMET ENTREPRENØR AS has its business address in Oslo.

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.