BIZTRAC BETA
Computer consultancy and computer facilities management activities

LEASI AS

Org. no. 929534603 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 4.0m
Operating profit NOK −2.7m
Equity NOK 3.8m
Incorporated 2022
Employees 9
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,7 mill kr).

LEASI AS is registered as a limited company in Oslo, Oslo with organisation number 929534603. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2022 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen Programvare - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.0m in revenue and NOK −2.7m in operating profit.

Key figures · 2024

Revenue
NOK 4.0m
Operating profit
NOK −2.7m
Equity
NOK 3.8m
Est. value
NOK 7.5m

Financial health · 2024

Liquidity
6.49
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
56.6%
Very good
Equity as a share of total capital

Who owns LEASI AS?

BALCON HOLDING AS
LEASI AS
NOK 4.0m rev. · NOK −2.7m profit

LEASI AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEASI AS

Who owns LEASI AS?

BALCON HOLDING AS is the largest registered owner, with 31.3%.

What is the revenue of LEASI AS?

LEASI AS had revenue of NOK 4.0m in 2024.

Who is the general manager of LEASI AS?

Scott Aleksander Bekke is registered as general manager of LEASI AS.

Where is LEASI AS based?

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