BIZTRAC BETA
Rental and operating of own or leased real estate

STEENSTRUP NÆRINGSBYGG AS

Org. no. 996868788 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 17.2m
Operating profit NOK 13.0m
Equity NOK 101.6m
Incorporated 2011
Share capital NOK 300,000

Signals

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

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

Key figures · 2024

Revenue
NOK 17.2m
Operating profit
NOK 13.0m
Equity
NOK 101.6m
Est. value
NOK 101.8m

Financial health · 2024

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

Who owns STEENSTRUP NÆRINGSBYGG AS?

KTP HOLDING II AS
STEENSTRUP NÆRINGSBYGG AS
NOK 17.2m rev. · NOK 13.0m profit

STEENSTRUP NÆRINGSBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STEENSTRUP NÆRINGSBYGG AS

Who owns STEENSTRUP NÆRINGSBYGG AS?

KTP HOLDING II AS is the largest registered owner, with 100.0%.

What is the revenue of STEENSTRUP NÆRINGSBYGG AS?

STEENSTRUP NÆRINGSBYGG AS had revenue of NOK 17.2m in 2024.

Where is STEENSTRUP NÆRINGSBYGG AS based?

STEENSTRUP NÆRINGSBYGG 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.