BIZTRAC BETA
Computer programming activities

TESTFLOW AS

Org. no. 928469824 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 5.5m
Operating profit NOK 569,000
Equity NOK −806,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−806k kr).

TESTFLOW AS is registered as a limited company in Oslo, Oslo with organisation number 928469824. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen digital brukertesting -og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.5m in revenue and NOK 569,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.5m
Operating profit
NOK 569,000
Equity
NOK −806,000
Est. value
NOK 6.4m

Financial health · 2024

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

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

Who owns TESTFLOW AS?

HAUGLID HOLDING AS
TESTFLOW AS
NOK 5.5m rev. · NOK 569,000 profit

TESTFLOW AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TESTFLOW AS

Who owns TESTFLOW AS?

HAUGLID HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of TESTFLOW AS?

TESTFLOW AS had revenue of NOK 5.5m in 2024.

Who is the general manager of TESTFLOW AS?

Erik Hauglid is registered as general manager of TESTFLOW AS.

Where is TESTFLOW AS based?

TESTFLOW AS has its business address in Oslo.

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.