BIZTRAC BETA
Motion picture and video distribution activities

DIGISTEP AS

Org. no. 916620020 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 477,000
Equity NOK 880,000
Incorporated 2016
Share capital NOK 30,000

DIGISTEP AS is registered as a limited company in Oslo, Oslo with organisation number 916620020. The business is classified under motion picture and video distribution activities (NACE 59.130). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulentvirksomhet innenfor forretningsutviklig og digitalisering. Selskapet kan også drive med utleie av teknisk utstyr tilknyttet dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 477,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 477,000
Equity
NOK 880,000
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns DIGISTEP AS?

PEDER BJØRGE KRISTIANSEN
DIGISTEP AS
NOK 1.3m rev. · NOK 477,000 profit

DIGISTEP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DIGISTEP AS own?

DIGISTEP AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about DIGISTEP AS

Who owns DIGISTEP AS?

PEDER BJØRGE KRISTIANSEN is the largest registered owner, with 100.0%.

What is the revenue of DIGISTEP AS?

DIGISTEP AS had revenue of NOK 1.3m in 2025.

Who is the general manager of DIGISTEP AS?

Peder Bjørge Kristiansen is registered as general manager of DIGISTEP AS.

Where is DIGISTEP AS based?

DIGISTEP 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.