BIZTRAC BETA
Construction of residential and non-residential buildings

STERK BYGG AS

Org. no. 917594619 Limited company (AS) Sarpsborg Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 15.4m
Operating profit NOK 3.2m
Equity NOK 3.3m
Incorporated 2016
Employees 15
Share capital NOK 30,000

STERK BYGG AS is registered as a limited company in Sarpsborg, Østfold with organisation number 917594619. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016 and has 15 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Gipsmontører- og tømrertjenester innenfor byggebransjen og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet driver også med kjøp, salg og utleie av bolig.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.4m in revenue and NOK 3.2m in operating profit.

Key figures · 2024

Revenue
NOK 15.4m
Operating profit
NOK 3.2m
Equity
NOK 3.3m
Est. value
NOK 11.0m

Financial health · 2024

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

Who owns STERK BYGG AS?

LEHEL ERÖSS
STERK BYGG AS
NOK 15.4m rev. · NOK 3.2m profit

STERK BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STERK BYGG AS

Who owns STERK BYGG AS?

LEHEL ERÖSS is the largest registered owner, with 100.0%.

What is the revenue of STERK BYGG AS?

STERK BYGG AS had revenue of NOK 15.4m in 2024.

Where is STERK BYGG AS based?

STERK BYGG AS has its business address in Ise.

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.