biztrac. BETA
COMPANY REGISTER PROFILE
928702456 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Computer consultancy and computer facilities management activities

LCORP AS

Org. no. 928702456 Limited company (AS) Ålesund Incorporated 2022 Active
Revenue 2025 NOK 9.4m
Operating profit NOK 401,000
Equity NOK 766,000
Incorporated 2022
Share capital NOK 30,000

LCORP AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 928702456. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen IT og nettbutikk drift - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.4m in revenue and NOK 401,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.4m
▲ +78 %
Operating profit
NOK 401,000
▲ +583 %
Equity
NOK 766,000
▲ +773 %
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns LCORP AS?

LCORP AS
NOK 9.4m rev. · NOK 401,000 profit

LCORP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LCORP AS

Who owns LCORP AS?

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

What is the revenue of LCORP AS?

LCORP AS had revenue of NOK 9.4m in 2025.

Who is the general manager of LCORP AS?

Hussein Dib is registered as general manager of LCORP AS.

Where is LCORP AS based?

LCORP AS has its business address in Ålesund.

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.