biztrac. BETA
COMPANY REGISTER PROFILE
936581706 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of adventure companies

ELISUM AS

Org. no. 936581706 Limited company (AS) Oslo Incorporated 2025 Active
Revenue 2025 NOK 149,000
Operating profit NOK 49,000
Equity NOK 68,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-10-29.

ELISUM AS is registered as a limited company in Oslo, Oslo with organisation number 936581706. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Organisering av eksklusive arrangementer, eventplanlegging, concierge-tjenester, utvikling av konsepter for bar- og cocktailopplevelser, samt relaterte tjenester i Norge og internasjonalt.”. The most recent filed accounts, for the 2025 financial year, show NOK 149,000 in revenue and NOK 49,000 in operating profit.

Key figures · 2025

Revenue
NOK 149,000
Operating profit
NOK 49,000
Equity
NOK 68,000
Est. value
NOK 189,000

Financial health · 2025

Liquidity
4.95
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
79.8%
Weak
Equity as a share of total capital

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

Who owns ELISUM AS?

ELISUM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ELISUM AS

Who owns ELISUM AS?

Orges Duro is the largest registered owner, with 33.3%.

What is the revenue of ELISUM AS?

ELISUM AS had revenue of NOK 149,000 in 2025.

Who is the general manager of ELISUM AS?

Orges Duro is registered as general manager of ELISUM AS.

Where is ELISUM AS based?

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