BIZTRAC BETA
Rental and operating of own or leased real estate

VOGNVEGEN 28 AS

Org. no. 822213022 Limited company (AS) Eidsvoll Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 733,000
Equity NOK 8.8m
Incorporated 2019
Share capital NOK 200,000

Signals

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

VOGNVEGEN 28 AS is registered as a limited company in Eidsvoll, Akershus with organisation number 822213022. 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 200,000, divided into 1000 shares. The company's stated purpose is: “Oppføring, forvaltning og utleie av eiendommer, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 733,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 733,000
Equity
NOK 8.8m
Est. value
NOK 7.1m

Financial health · 2024

Liquidity
5.77
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.3%
Good
Equity as a share of total capital

Who owns VOGNVEGEN 28 AS?

IDEHUS ROMERIKE HOLDING AS
VOGNVEGEN 28 AS
NOK 2.1m rev. · NOK 733,000 profit

VOGNVEGEN 28 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VOGNVEGEN 28 AS

Who owns VOGNVEGEN 28 AS?

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

What is the revenue of VOGNVEGEN 28 AS?

VOGNVEGEN 28 AS had revenue of NOK 2.1m in 2024.

Who is the general manager of VOGNVEGEN 28 AS?

Pål Østby is registered as general manager of VOGNVEGEN 28 AS.

Where is VOGNVEGEN 28 AS based?

VOGNVEGEN 28 AS has its business address in Dal.

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.