BIZTRAC BETA
Rental and operating of own or leased real estate

STERKODER AS

Org. no. 916268459 Limited company (AS) Oslo Incorporated 1935 Active
Ownership graph ↗
Revenue 2024 NOK 32.5m
Operating profit NOK 11.3m
Equity NOK 26.0m
Incorporated 1935
Share capital NOK 900,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STERKODER AS is registered as a limited company in Oslo, Oslo with organisation number 916268459. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1935. Registered share capital is NOK 900,000, divided into 9000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 32.5m in revenue and NOK 11.3m in operating profit.

Key figures · 2024

Revenue
NOK 32.5m
Operating profit
NOK 11.3m
Equity
NOK 26.0m
Est. value
NOK 37.1m

Financial health · 2024

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.0%
Satisfactory
Equity as a share of total capital

Who owns STERKODER AS?

ASSET BUYOUT PARTNERS AS
STERKODER AS
NOK 32.5m rev. · NOK 11.3m profit

STERKODER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STERKODER AS own?

STERKODER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STERKODER AS

Who owns STERKODER AS?

ASSET BUYOUT PARTNERS AS is the largest registered owner, with 100.0%.

What is the revenue of STERKODER AS?

STERKODER AS had revenue of NOK 32.5m in 2024.

Where is STERKODER AS based?

STERKODER 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.