BIZTRAC BETA
Development of building projects

WEIDEMANNS VEI EIENDOMSUTVIKLING AS

Org. no. 920336876 Limited company (AS) Larvik Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 1.9m
Equity NOK 8.7m
Incorporated 2018
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.

WEIDEMANNS VEI EIENDOMSUTVIKLING AS is registered as a limited company in Larvik, Vestfold with organisation number 920336876. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie og utvikle eiendom i Weidemanns vei.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 1.9m
Equity
NOK 8.7m
Est. value
NOK 9.6m

Financial health · 2024

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

Who owns WEIDEMANNS VEI EIENDOMSUTVIKLING AS?

NIDELVEN EIENDOM AS
WEIDEMANNS VEI EIENDOMSUTVIKLING AS
NOK 2.0m rev. · NOK 1.9m profit

WEIDEMANNS VEI EIENDOMSUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WEIDEMANNS VEI EIENDOMSUTVIKLING AS

Who owns WEIDEMANNS VEI EIENDOMSUTVIKLING AS?

NIDELVEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of WEIDEMANNS VEI EIENDOMSUTVIKLING AS?

WEIDEMANNS VEI EIENDOMSUTVIKLING AS had revenue of NOK 2.0m in 2024.

Where is WEIDEMANNS VEI EIENDOMSUTVIKLING AS based?

WEIDEMANNS VEI EIENDOMSUTVIKLING 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.