BIZTRAC BETA
COMPANY REGISTER PROFILE
935575869 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

LUSORIA AS

Org. no. 935575869 Limited company (AS) Stjørdal Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK 1.1m
Incorporated 2025
Share capital NOK 53,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).

LUSORIA AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 935575869. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 53,000, divided into 222 shares. The company's stated purpose is: “Investere og eie aksjer i andre selskap, samt alt som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −21,000
Equity
NOK 1.1m
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
0.44
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.7%
Good
Equity as a share of total capital

Who owns LUSORIA AS?

LUSORIA AS
· NOK −21,000 profit

LUSORIA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LUSORIA AS own?

LUSORIA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LUSORIA AS

Who owns LUSORIA AS?

HEGE VIKAUNE is the largest registered owner, with 100.0%.

Where is LUSORIA AS based?

LUSORIA AS has its business address in Stjørdal.

Property

Business address Ydstinesvegen 46, 7514 Stjørdal
Cadastral unit 5035-108/95/0/0
Building Enebolig · 2 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.