BIZTRAC BETA
Other technical consultancy

SJULASS AS

Org. no. 916695942 Limited company (AS) Bærum Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3,000
Equity NOK 253,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

SJULASS AS is registered as a limited company in Bærum, Akershus with organisation number 916695942. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av aksjer samt deltagelse i andre selskaper/virksomheter. Selskapet skal også drive konsulentvirksomhet ved å yte ingeniørtjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 253,000
Est. value
NOK 411,000

Financial health · 2024

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

Who owns SJULASS AS?

SJUR LASSESEN
SJULASS AS
NOK 0 rev. · NOK −3,000 profit

SJULASS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SJULASS AS own?

SJULASS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SJULASS AS

Who owns SJULASS AS?

SJUR LASSESEN is the largest registered owner, with 100.0%.

What is the revenue of SJULASS AS?

SJULASS AS had revenue of NOK 0 in 2024.

Who is the general manager of SJULASS AS?

Sjur Lassesen is registered as general manager of SJULASS AS.

Where is SJULASS AS based?

SJULASS AS has its business address in Stabekk.

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.