biztrac. BETA
COMPANY REGISTER PROFILE
936865550 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠LEIV AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Computer programming activities

LEIV AS

Org. no. 936865550 Limited company (AS) Ullensaker Incorporated 2025 In liquidation
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Nystiftet selskap Selskapet ble stiftet 2025-11-04.

LEIV AS is registered as a limited company in Ullensaker, Akershus with organisation number 936865550. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling av teknologi og annen virksomhet som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000

Financial health · 2025

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

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

Who owns LEIV AS?

LEIV AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEIV AS

Who owns LEIV AS?

JUTUS SKANDINAVIA AS is the largest registered owner, with 50.0%.

What is the revenue of LEIV AS?

LEIV AS had revenue of NOK 0 in 2025.

Who is the general manager of LEIV AS?

Espen Sørlie is registered as general manager of LEIV AS.

Where is LEIV AS based?

LEIV AS has its business address in Jessheim.

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.