BIZTRAC BETA
Development of building projects

INVEST'DA AS

Org. no. 933107558 Limited company (AS) Kvam Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −862
Equity NOK 23,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−862 kr).

INVEST'DA AS is registered as a limited company in Kvam, Vestland with organisation number 933107558. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i, eie, forvalte og selge andeler i andre selskaper, samt å utøve aktiviteter som er komplementære til disse, inkludert, men ikke begrenset til, finansiell rådgivning og forvaltning.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −862 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −862
Equity
NOK 23,000
Est. value
NOK 21,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns INVEST'DA AS?

BYGGDA GRUPPEN AS
INVEST'DA AS
NOK 0 rev. · NOK −862 profit

INVEST'DA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does INVEST'DA AS own?

INVEST'DA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about INVEST'DA AS

Who owns INVEST'DA AS?

BYGGDA GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of INVEST'DA AS?

INVEST'DA AS had revenue of NOK 0 in 2024.

Where is INVEST'DA AS based?

INVEST'DA AS has its business address in Omastrand.

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.