BIZTRAC BETA
Development of building projects

ENGELSRUDHAGEN S1 AS

Org. no. 913981456 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −48,000
Equity NOK 583,000
Incorporated 2014
Share capital NOK 1.5m

Signals

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

ENGELSRUDHAGEN S1 AS is registered as a limited company in Oslo, Oslo with organisation number 913981456. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 1.5m, divided into 358260 shares. The company's stated purpose is: “Kjøp, utvikling og salg av tomter og fast eiendom, samt enhver virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −48,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −48,000
Equity
NOK 583,000
Est. value
NOK 532,000

Financial health · 2024

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

Who owns ENGELSRUDHAGEN S1 AS?

ENGELSRUDHAGEN BOLIGTOMT FOND AS
ENGELSRUDHAGEN S1 AS
NOK 0 rev. · NOK −48,000 profit

ENGELSRUDHAGEN S1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENGELSRUDHAGEN S1 AS

Who owns ENGELSRUDHAGEN S1 AS?

ENGELSRUDHAGEN BOLIGTOMT FOND AS is the largest registered owner, with 100.0%.

What is the revenue of ENGELSRUDHAGEN S1 AS?

ENGELSRUDHAGEN S1 AS had revenue of NOK 0 in 2024.

Where is ENGELSRUDHAGEN S1 AS based?

ENGELSRUDHAGEN S1 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.