BIZTRAC BETA
Computer programming activities

ABENDUM AS

Org. no. 924359463 Limited company (AS) Ullensaker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 59,000
Operating profit NOK −4,000
Equity NOK −956,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−956k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

ABENDUM AS is registered as a limited company in Ullensaker, Akershus with organisation number 924359463. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling av digitale løsninger og tjenester innen informasjons-, finans- og blockchainteknologi.”. The most recent filed accounts, for the 2025 financial year, show NOK 59,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 59,000
Operating profit
NOK −4,000
Equity
NOK −956,000

Financial health · 2024

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

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

Who owns ABENDUM AS?

UNISOT HOLDING AS
ABENDUM AS
NOK 59,000 rev. · NOK −4,000 profit

ABENDUM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ABENDUM AS

Who owns ABENDUM AS?

UNISOT HOLDING AS is the largest registered owner, with 67.7%.

What is the revenue of ABENDUM AS?

ABENDUM AS had revenue of NOK 59,000 in 2025.

Who is the general manager of ABENDUM AS?

Lars Olle Stephan Nilsson is registered as general manager of ABENDUM AS.

Where is ABENDUM AS based?

ABENDUM AS has its business address in Kløfta.

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.