biztrac. BETA
COMPANY REGISTER PROFILE
985316856 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other educational support services n.e.c.

KOL AS

Org. no. 985316856 Limited company (AS) Kristiansand Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 324,000
Operating profit NOK 90,000
Equity NOK 174,000
Incorporated 2002
Share capital NOK 100,000

KOL AS is registered as a limited company in Kristiansand, Agder with organisation number 985316856. The business is classified under other educational support services n.e.c. (NACE 85.699). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester, katastrofeberedskap, endringsledelse, undervisning, kurs o.a. overfor høyskoler, næringsliv og organisasjoner.”. The most recent filed accounts, for the 2025 financial year, show NOK 324,000 in revenue and NOK 90,000 in operating profit.

Former names: KRISE ORGANISASJON LEDELSE AS

Key figures · 2025

Revenue
NOK 324,000
▼ −17 %
Operating profit
NOK 90,000
▼ −47 %
Equity
NOK 174,000
▲ +109 %
Est. value
NOK 514,000

Financial health · 2025

Liquidity
9.36
Very good
Current assets ÷ current liabilities
Profitability
59.4%
Very good
Return on total assets
Solidity
90.7%
Very good
Equity as a share of total capital

Who owns KOL AS?

KOL AS
NOK 324,000 rev. · NOK 90,000 profit

KOL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOL AS

Who owns KOL AS?

Renate Erika Charlotte Grønvold Bugge is the largest registered owner, with 100.0%.

What is the revenue of KOL AS?

KOL AS had revenue of NOK 324,000 in 2025.

Who is the general manager of KOL AS?

Renate Erika Charlotte Grønvold Bugge is registered as general manager of KOL AS.

Where is KOL AS based?

KOL AS has its business address in Kristiansand S.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.