biztrac. BETA
COMPANY REGISTER PROFILE
925178357 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

DIGIBRANN AS

Org. no. 925178357 Limited company (AS) Lørenskog Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 70,000
Equity NOK 1.0m
Incorporated 2020
Share capital NOK 155,000

DIGIBRANN AS is registered as a limited company in Lørenskog, Akershus with organisation number 925178357. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 155,000, divided into 155000 shares. The company's stated purpose is: “Utvikling, produksjon, salg, distribusjon og lisensiering av programvare, digitale løsninger og andre produkter/tjenester som naturlig hører sammen med dette, herunder deltakelse i andre selskaper med liknende virksomhet, og kjøp og salg av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 70,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
▲ +11 %
Operating profit
NOK 70,000
▼ −73 %
Equity
NOK 1.0m
▲ +6 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
1.25
Satisfactory
Current assets ÷ current liabilities
Profitability
5.0%
Weak
Return on total assets
Solidity
63.3%
Very good
Equity as a share of total capital

Who owns DIGIBRANN AS?

DIGIBRANN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about DIGIBRANN AS

Who owns DIGIBRANN AS?

FRANK AS is the largest registered owner, with 50.0%.

What is the revenue of DIGIBRANN AS?

DIGIBRANN AS had revenue of NOK 2.3m in 2025.

Who is the general manager of DIGIBRANN AS?

Frank Bredal is registered as general manager of DIGIBRANN AS.

Where is DIGIBRANN AS based?

DIGIBRANN AS has its business address in Fjellhamar.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.