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

KILE AS

Org. no. 924515473 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −60,000
Equity NOK 6.4m
Incorporated 2020
Share capital NOK 30,000

Signals

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

KILE AS is registered as a limited company in Oslo, Oslo with organisation number 924515473. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −60,000
▼ −681 %
Equity
NOK 6.4m
▲ +326 %
Est. value
NOK 35.6m

Financial health · 2025

Liquidity
60.11
Very good
Current assets ÷ current liabilities
Profitability
114.0%
Very good
Return on total assets
Solidity
99.0%
Very good
Equity as a share of total capital

Who owns KILE AS?

KILE AS
· NOK −60,000 profit

KILE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KILE AS own?

KILE AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about KILE AS

Who owns KILE AS?

KIM LEIKVANG is the largest registered owner, with 100.0%.

Where is KILE AS based?

KILE AS has its business address in Oslo.

Property

Business address Vækerøveien 159D, 0751 Oslo
Cadastral unit 301-11/89/0/0
Building Tomannsbolig, vertikal · 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.