BIZTRAC BETA
Buying and selling of own real estate

2504 - ISDAMVEIEN 24 S25 AS

Org. no. 935491916 Limited company (AS) Tønsberg Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 16,000
Operating profit NOK −22,000
Equity NOK 189,000
Incorporated 2025
Share capital NOK 94,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).

2504 - ISDAMVEIEN 24 S25 AS is registered as a limited company in Tønsberg, Vestfold with organisation number 935491916. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 94,000, divided into 300 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, utleie av fast eiendom og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 16,000 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 16,000
Operating profit
NOK −22,000
Equity
NOK 189,000
Est. value
NOK 154,000

Financial health · 2025

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

Who owns 2504 - ISDAMVEIEN 24 S25 AS?

VESTFOLD UTVIKLING AS
2504 - ISDAMVEIEN 24 S25 AS
NOK 16,000 rev. · NOK −22,000 profit

2504 - ISDAMVEIEN 24 S25 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 2504 - ISDAMVEIEN 24 S25 AS

Who owns 2504 - ISDAMVEIEN 24 S25 AS?

VESTFOLD UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of 2504 - ISDAMVEIEN 24 S25 AS?

2504 - ISDAMVEIEN 24 S25 AS had revenue of NOK 16,000 in 2025.

Where is 2504 - ISDAMVEIEN 24 S25 AS based?

2504 - ISDAMVEIEN 24 S25 AS has its business address in Barkåker.

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.