BIZTRAC BETA
Rental and operating of own or leased real estate

ELVEVEIEN 35 AS

Org. no. 923244646 Limited company (AS) Larvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 87,000
Operating profit NOK 51,000
Equity NOK 214,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

ELVEVEIEN 35 AS is registered as a limited company in Larvik, Vestfold with organisation number 923244646. 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 500 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom, herunder utleie av fast eiendom til næringsformål.”. The most recent filed accounts, for the 2025 financial year, show NOK 87,000 in revenue and NOK 51,000 in operating profit.

Key figures · 2025

Revenue
NOK 87,000
Operating profit
NOK 51,000
Equity
NOK 214,000
Est. value
NOK 275,000

Financial health · 2025

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

Who owns ELVEVEIEN 35 AS?

FRITZØE EIENDOM UTVIKLING AS
ELVEVEIEN 35 AS
NOK 87,000 rev. · NOK 51,000 profit

ELVEVEIEN 35 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ELVEVEIEN 35 AS er morselskap for 51 datterselskaper:

Frequently asked questions about ELVEVEIEN 35 AS

Who owns ELVEVEIEN 35 AS?

FRITZØE EIENDOM UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of ELVEVEIEN 35 AS?

ELVEVEIEN 35 AS had revenue of NOK 87,000 in 2025.

Where is ELVEVEIEN 35 AS based?

ELVEVEIEN 35 AS has its business address in Larvik.

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.