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

KELIS AS

Org. no. 931392832 Limited company (AS) Bjørnafjorden Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −6
Equity NOK 496,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

KELIS AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 931392832. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og fast eiendom og andre produkter/tjenester som naturlig hører sammen med dette.”.

Key figures · 2025

Operating profit
NOK −6
▼ −100 %
Equity
NOK 496,000
▲ +1933 %
Est. value
NOK 3.4m

Financial health · 2025

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

Who owns KELIS AS?

KELIS AS
· NOK −6 profit

KELIS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KELIS AS own?

KELIS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KELIS AS

Who owns KELIS AS?

KENNETH JENSEN is the largest registered owner, with 100.0%.

Where is KELIS AS based?

KELIS AS has its business address in Os.

Property

Business address Vågshaugen 46, 5209 Os
Cadastral unit 4624-51/276/0/0
Building Enebolig · 1 unit

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.