BIZTRAC BETA
Buying and selling of own real estate

BLÅKLOKKE INVEST AS

Org. no. 935444896 Limited company (AS) Tolga Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −863
Equity NOK 32,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

BLÅKLOKKE INVEST AS is registered as a limited company in Tolga, Innlandet with organisation number 935444896. 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 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i andre selskaper, herunder kjøp og salg av aksjer, samt kjøp og salg av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −863 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −863
Equity
NOK 32,000
Est. value
NOK 58,000

Financial health · 2025

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

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

Who owns BLÅKLOKKE INVEST AS?

INGUNN FLAA
BLÅKLOKKE INVEST AS
NOK 0 rev. · NOK −863 profit

BLÅKLOKKE INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BLÅKLOKKE INVEST AS own?

BLÅKLOKKE INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLÅKLOKKE INVEST AS

Who owns BLÅKLOKKE INVEST AS?

INGUNN FLAA is the largest registered owner, with 100.0%.

What is the revenue of BLÅKLOKKE INVEST AS?

BLÅKLOKKE INVEST AS had revenue of NOK 0 in 2025.

Where is BLÅKLOKKE INVEST AS based?

BLÅKLOKKE INVEST AS has its business address in Vingelen.

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.