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

ÅSENVEIEN PARK AS

Org. no. 929275284 Limited company (AS) Oslo Incorporated 2022 Active
Revenue 2025 NOK 923,000
Operating profit NOK 524,000
Equity NOK 5.9m
Incorporated 2022
Share capital NOK 100,000

Signals

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

ÅSENVEIEN PARK AS is registered as a limited company in Oslo, Oslo with organisation number 929275284. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer, andel og fast eiendom med fokus på boligutvikling, utleie og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 923,000 in revenue and NOK 524,000 in operating profit.

Key figures · 2025

Revenue
NOK 923,000
▲ +1 %
Operating profit
NOK 524,000
▼ −11 %
Equity
NOK 5.9m
▲ +1859 %
Est. value
NOK 4.9m

Financial health · 2025

Liquidity
129.72
Very good
Current assets ÷ current liabilities
Profitability
2.7%
Weak
Return on total assets
Solidity
31.4%
Good
Equity as a share of total capital

Who owns ÅSENVEIEN PARK AS?

ÅSENVEIEN PARK AS
NOK 923,000 rev. · NOK 524,000 profit

ÅSENVEIEN PARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅSENVEIEN PARK AS

Who owns ÅSENVEIEN PARK AS?

EMGODS BOLIG AS is the largest registered owner, with 100.0%.

What is the revenue of ÅSENVEIEN PARK AS?

ÅSENVEIEN PARK AS had revenue of NOK 923,000 in 2025.

Where is ÅSENVEIEN PARK AS based?

ÅSENVEIEN PARK 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 03.10.2026.

Report a problem

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