BIZTRAC BETA
Civil engineering activities

KOLKIE AS

Org. no. 915854796 Limited company (AS) Asker Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 18,000
Operating profit NOK −32,000
Equity NOK 624,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

KOLKIE AS is registered as a limited company in Asker, Akershus with organisation number 915854796. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å drive konsulent- og prosjektarbeid innenfor byggenæringen, samt oppføring og renovering av bygninger og salg og utleie av bygninger. Investeringer i eiendom og aksjer i inn og utland og hva dermed står i forbindelse”. The most recent filed accounts, for the 2025 financial year, show NOK 18,000 in revenue and NOK −32,000 in operating profit.

Key figures · 2025

Revenue
NOK 18,000
Operating profit
NOK −32,000
Equity
NOK 624,000
Est. value
NOK 323,000

Financial health · 2025

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

Who owns KOLKIE AS?

PER CHRISTIAN KIELLAND
KOLKIE AS
NOK 18,000 rev. · NOK −32,000 profit

KOLKIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOLKIE AS

Who owns KOLKIE AS?

PER CHRISTIAN KIELLAND is the largest registered owner, with 100.0%.

What is the revenue of KOLKIE AS?

KOLKIE AS had revenue of NOK 18,000 in 2025.

Who is the general manager of KOLKIE AS?

Per Christian Kielland is registered as general manager of KOLKIE AS.

Where is KOLKIE AS based?

KOLKIE AS has its business address in Borgen.

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.