BIZTRAC BETA
Office administrative and support activities

DEPONA AS

Org. no. 992530995 Limited company (AS) Oslo Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK −1.1m
Equity NOK −11.9m
Incorporated 2008
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−11,9 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,1 mill kr).

DEPONA AS is registered as a limited company in Oslo, Oslo with organisation number 992530995. The business is classified under office administrative and support activities (NACE 82.100). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Dokumenthåndteringstjenester samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK −1.1m
Equity
NOK −11.9m

Financial health · 2024

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

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

Who owns DEPONA AS?

DEPONA AB
DEPONA AS
NOK 1.7m rev. · NOK −1.1m profit

DEPONA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DEPONA AS

Who owns DEPONA AS?

DEPONA AB is the largest registered owner, with 100.0%.

What is the revenue of DEPONA AS?

DEPONA AS had revenue of NOK 1.7m in 2024.

Who is the general manager of DEPONA AS?

Carl Magnus Litens is registered as general manager of DEPONA AS.

Where is DEPONA AS based?

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