BIZTRAC BETA
Development of building projects

TANDBERGÅSEN INVEST AS

Org. no. 928180174 Limited company (AS) Holmestrand Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −57,000
Equity NOK 546,000
Incorporated 2021
Share capital NOK 105,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−57k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TANDBERGÅSEN INVEST AS is registered as a limited company in Holmestrand, Vestfold with organisation number 928180174. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 105,000, divided into 1045 shares. The company's stated purpose is: “Utvikling, forvaltning og omsetning av eiendom, samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −57,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −57,000
Equity
NOK 546,000
Est. value
NOK 498,000

Financial health · 2024

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

Who owns TANDBERGÅSEN INVEST AS?

JIL INVEST AS
TANDBERGÅSEN INVEST AS
NOK 0 rev. · NOK −57,000 profit

TANDBERGÅSEN INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TANDBERGÅSEN INVEST AS

Who owns TANDBERGÅSEN INVEST AS?

JIL INVEST AS is the largest registered owner, with 80.0%.

What is the revenue of TANDBERGÅSEN INVEST AS?

TANDBERGÅSEN INVEST AS had revenue of NOK 0 in 2024.

Where is TANDBERGÅSEN INVEST AS based?

TANDBERGÅSEN INVEST AS has its business address in Sande I Vestfold.

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.