BIZTRAC BETA
COMPANY REGISTER PROFILE
923535268 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

LJET AS

Org. no. 923535268 Limited company (AS) Lillestrøm Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 100,000
Operating profit NOK −413,000
Equity NOK 1.5m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−413k kr).

LJET AS is registered as a limited company in Lillestrøm, Akershus with organisation number 923535268. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i og forvaltning av verdipapirer, herunder aksjer, og salg av rådgivningstjenester. Videre kjøp, salg og forvaltning av fast eiendom samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 100,000 in revenue and NOK −413,000 in operating profit.

Key figures · 2024

Revenue
NOK 100,000
Operating profit
NOK −413,000
Equity
NOK 1.5m
Est. value
NOK 863,000

Financial health · 2024

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

Who owns LJET AS?

KNUT SIGMUND LØVSTAD
LJET AS
NOK 100,000 rev. · NOK −413,000 profit

LJET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LJET AS

Who owns LJET AS?

KNUT SIGMUND LØVSTAD is the largest registered owner, with 100.0%.

What is the revenue of LJET AS?

LJET AS had revenue of NOK 100,000 in 2024.

Who is the general manager of LJET AS?

Knut Sigmund Løvstad is registered as general manager of LJET AS.

Where is LJET AS based?

LJET AS has its business address in Lillestrøm.

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.