BIZTRAC BETA
Buying and selling of own real estate

VULUVEGEN 258 NÆRING AS

Org. no. 923150161 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 7,000
Equity NOK 3.0m
Incorporated 2019
Share capital NOK 60,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-02-03 Adresseendring registrert 2026-02-03.

VULUVEGEN 258 NÆRING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 923150161. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling med naturlig tilknyttet virksomhet, samt å investere i annen type virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 7,000
Equity
NOK 3.0m
Est. value
NOK 2.0m

Financial health · 2024

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.9%
Good
Equity as a share of total capital

Who owns VULUVEGEN 258 NÆRING AS?

ECO HOLDING AS
VULUVEGEN 258 NÆRING AS
NOK 0 rev. · NOK 7,000 profit

VULUVEGEN 258 NÆRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VULUVEGEN 258 NÆRING AS

Who owns VULUVEGEN 258 NÆRING AS?

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

What is the revenue of VULUVEGEN 258 NÆRING AS?

VULUVEGEN 258 NÆRING AS had revenue of NOK 0 in 2024.

Where is VULUVEGEN 258 NÆRING AS based?

VULUVEGEN 258 NÆRING AS has its business address in Ranheim.

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.