BIZTRAC BETA
Uoppgitt

FREEFLOW AS

Org. no. 932402157 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 475,000
Operating profit NOK −60,000
Equity NOK −37,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−37k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−60k kr).

FREEFLOW AS is registered as a limited company in Trondheim, Trøndelag with organisation number 932402157. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investere i andre selskaper og prosjekter.”. The most recent filed accounts, for the 2024 financial year, show NOK 475,000 in revenue and NOK −60,000 in operating profit.

Key figures · 2024

Revenue
NOK 475,000
Operating profit
NOK −60,000
Equity
NOK −37,000

Financial health · 2024

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

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

Who owns FREEFLOW AS?

PETTER BJERKLI
FREEFLOW AS
NOK 475,000 rev. · NOK −60,000 profit

FREEFLOW AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FREEFLOW AS own?

FREEFLOW AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FREEFLOW AS

Who owns FREEFLOW AS?

PETTER BJERKLI is the largest registered owner, with 50.0%.

What is the revenue of FREEFLOW AS?

FREEFLOW AS had revenue of NOK 475,000 in 2024.

Who is the general manager of FREEFLOW AS?

Inger Hjelde Ekli is registered as general manager of FREEFLOW AS.

Where is FREEFLOW AS based?

FREEFLOW AS has its business address in Trondheim.

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.