biztrac. BETA
COMPANY REGISTER PROFILE
931810324 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

ENGELSRUDHAGEN AS

Org. no. 931810324 Limited company (AS) Ullensaker Incorporated 2023 Active
Revenue 2025 NOK 0
Operating profit NOK −40,000
Equity NOK 10.6m
Incorporated 2023
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−40k kr).

ENGELSRUDHAGEN AS is registered as a limited company in Ullensaker, Akershus with organisation number 931810324. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 200 shares. The company's stated purpose is: “Kjøp, drift, utvikling, salg og utleie av fast eiendom og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −40,000 in operating profit.

Former names: WEENBO ENGELSRUDHAGEN AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −40,000
▼ −59 %
Equity
NOK 10.6m
▲ +178 %
Est. value
NOK 9.6m

Financial health · 2025

Liquidity
4.47
Very good
Current assets ÷ current liabilities
Profitability
-0.1%
Not satisfactory
Return on total assets
Solidity
21.6%
Good
Equity as a share of total capital

Who owns ENGELSRUDHAGEN AS?

ENGELSRUDHAGEN AS
NOK 0 rev. · NOK −40,000 profit

ENGELSRUDHAGEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ENGELSRUDHAGEN AS

Who owns ENGELSRUDHAGEN AS?

WEENBO EIENDOM AS is the largest registered owner, with 59.9%.

What is the revenue of ENGELSRUDHAGEN AS?

ENGELSRUDHAGEN AS had revenue of NOK 0 in 2025.

Where is ENGELSRUDHAGEN AS based?

ENGELSRUDHAGEN AS has its business address in Jessheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.