BIZTRAC BETA
COMPANY REGISTER PROFILE
918457704 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Computer consultancy and computer facilities management activities

BITFLOW SOLUTIONS AS

Org. no. 918457704 Limited company (AS) Øvre Eiker Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 303,000
Operating profit NOK −184,000
Equity NOK 1.1m
Incorporated 2017
Share capital NOK 30,000

Signals

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

BITFLOW SOLUTIONS AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 918457704. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “IT- og programmeringstjenester/konsultasjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 303,000 in revenue and NOK −184,000 in operating profit.

Key figures · 2025

Revenue
NOK 303,000
Operating profit
NOK −184,000
Equity
NOK 1.1m
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns BITFLOW SOLUTIONS AS?

PÅL MATHIAS ELLEFSEN
BITFLOW SOLUTIONS AS
NOK 303,000 rev. · NOK −184,000 profit

BITFLOW SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BITFLOW SOLUTIONS AS

Who owns BITFLOW SOLUTIONS AS?

PÅL MATHIAS ELLEFSEN is the largest registered owner, with 100.0%.

What is the revenue of BITFLOW SOLUTIONS AS?

BITFLOW SOLUTIONS AS had revenue of NOK 303,000 in 2025.

Where is BITFLOW SOLUTIONS AS based?

BITFLOW SOLUTIONS AS has its business address in Hokksund.

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.