BIZTRAC BETA
Computer consultancy and computer facilities management activities

DIGITALISERINGSPARTNER AS

Org. no. 924348224 Limited company (AS) Bærum Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −31,000
Equity NOK 178,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

DIGITALISERINGSPARTNER AS is registered as a limited company in Bærum, Akershus with organisation number 924348224. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “IT-tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −31,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −31,000
Equity
NOK 178,000
Est. value
NOK 323,000

Financial health · 2025

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

Who owns DIGITALISERINGSPARTNER AS?

SENSER AS
DIGITALISERINGSPARTNER AS
NOK 0 rev. · NOK −31,000 profit

DIGITALISERINGSPARTNER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DIGITALISERINGSPARTNER AS

Who owns DIGITALISERINGSPARTNER AS?

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

What is the revenue of DIGITALISERINGSPARTNER AS?

DIGITALISERINGSPARTNER AS had revenue of NOK 0 in 2025.

Who is the general manager of DIGITALISERINGSPARTNER AS?

Ottar Sylte is registered as general manager of DIGITALISERINGSPARTNER AS.

Where is DIGITALISERINGSPARTNER AS based?

DIGITALISERINGSPARTNER AS has its business address in Blommenholm.

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.