BIZTRAC BETA
Rental and operating of own or leased real estate

ENGOMSVINGEN 23-25 AS

Org. no. 923837035 Limited company (AS) Ullensaker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 712,000
Equity NOK 1.1m
Incorporated 2019
Share capital NOK 30,000

ENGOMSVINGEN 23-25 AS is registered as a limited company in Ullensaker, Akershus with organisation number 923837035. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utleie av fast eiendom og andre tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender samt kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 712,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 712,000
Equity
NOK 1.1m
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns ENGOMSVINGEN 23-25 AS?

MALUS HOLDING AS
ENGOMSVINGEN 23-25 AS
NOK 1.1m rev. · NOK 712,000 profit

ENGOMSVINGEN 23-25 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENGOMSVINGEN 23-25 AS

Who owns ENGOMSVINGEN 23-25 AS?

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

What is the revenue of ENGOMSVINGEN 23-25 AS?

ENGOMSVINGEN 23-25 AS had revenue of NOK 1.1m in 2024.

Where is ENGOMSVINGEN 23-25 AS based?

ENGOMSVINGEN 23-25 AS has its business address in Kløfta.

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.