biztrac. BETA
COMPANY REGISTER PROFILE
993789585 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of information and communication equipment

AGDER KONTORUTSTYR AS

Org. no. 993789585 Limited company (AS) Oslo Incorporated 2009 Active
Ownership graph ↗
Operating profit NOK −24,000
Equity NOK −24,000
Incorporated 2009
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−24k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−24k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AGDER KONTORUTSTYR AS is registered as a limited company in Oslo, Oslo with organisation number 993789585. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2009. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av kontorutstyr og emballering, samt alt som står i forbindelse med dette, herunder konsulenttjenester, kjøp og salg. Selskapet kan delta i andre virksomheter.”.

Key figures · 2025

Operating profit
NOK −24,000
Equity
NOK −24,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

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

Who owns AGDER KONTORUTSTYR AS?

AGDER KONTORUTSTYR AS
· NOK −24,000 profit

AGDER KONTORUTSTYR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AGDER KONTORUTSTYR AS

Who owns AGDER KONTORUTSTYR AS?

WIBORG HOLDING AS is the largest registered owner, with 100.0%.

Where is AGDER KONTORUTSTYR AS based?

AGDER KONTORUTSTYR 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 03.10.2026.

Report a problem

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