BIZTRAC BETA
COMPANY REGISTER PROFILE
989117726 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

LEIOSS AS

Org. no. 989117726 Limited company (AS) Færder Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −15,000
Equity NOK 1.3m
Incorporated 2005
Share capital NOK 100,000

Signals

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

LEIOSS AS is registered as a limited company in Færder, Vestfold with organisation number 989117726. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 90 shares. The company's stated purpose is: “Investeringsvirksomhet og næringsutvikling.”.

Key figures · 2025

Operating profit
NOK −15,000
Equity
NOK 1.3m
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns LEIOSS AS?

LEIOSS AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LEIOSS AS own?

LEIOSS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LEIOSS AS

Who owns LEIOSS AS?

INDIMA AS is the largest registered owner, with 33.3%.

Where is LEIOSS AS based?

LEIOSS AS has its business address in Husøysund.

Property

Business address Haugåkerveien 60, 3132 Husøysund
Cadastral unit 3911-19/145/0/0
Building Enebolig · 1 unit

2 companies are registered at this address.

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.