BIZTRAC BETA
Construction of residential and non-residential buildings

NORGESHUS STS AS

Org. no. 927859971 Limited company (AS) Stjørdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 29.0m
Operating profit NOK −2.3m
Equity NOK 3.0m
Incorporated 2021
Employees 14
Share capital NOK 2.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,3 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NORGESHUS STS AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 927859971. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021 and has 14 registered employees. Registered share capital is NOK 2.0m, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet innen bygg og anlegg, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 29.0m in revenue and NOK −2.3m in operating profit.

Key figures · 2024

Revenue
NOK 29.0m
Operating profit
NOK −2.3m
Equity
NOK 3.0m
Est. value
NOK 11.4m

Financial health · 2024

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

Who owns NORGESHUS STS AS?

U9T INVEST AS
NORGESHUS STS AS
NOK 29.0m rev. · NOK −2.3m profit

NORGESHUS STS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORGESHUS STS AS

Who owns NORGESHUS STS AS?

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

What is the revenue of NORGESHUS STS AS?

NORGESHUS STS AS had revenue of NOK 29.0m in 2024.

Where is NORGESHUS STS AS based?

NORGESHUS STS AS has its business address in Stjørdal.

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.