BIZTRAC BETA
Other technical consultancy

KOLVIK & KROGSVEEN AS

Org. no. 919222050 Limited company (AS) Lillehammer Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 618,000
Equity NOK 1.1m
Incorporated 2017
Share capital NOK 30,000

KOLVIK & KROGSVEEN AS is registered as a limited company in Lillehammer, Innlandet with organisation number 919222050. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Programmering, prosjektering, drift og feilsøking på integrerte styringssystemer i bygg, energisentraler, ventilasjon, energirådgivning, ITB og tredjepartskontroll. Annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 618,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 618,000
Equity
NOK 1.1m
Est. value
NOK 3.7m

Financial health · 2025

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

Who owns KOLVIK & KROGSVEEN AS?

LARS KROGSVEEN
KOLVIK & KROGSVEEN AS
NOK 4.0m rev. · NOK 618,000 profit

KOLVIK & KROGSVEEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KOLVIK & KROGSVEEN AS

Who owns KOLVIK & KROGSVEEN AS?

LARS KROGSVEEN is the largest registered owner, with 50.0%.

What is the revenue of KOLVIK & KROGSVEEN AS?

KOLVIK & KROGSVEEN AS had revenue of NOK 4.0m in 2025.

Who is the general manager of KOLVIK & KROGSVEEN AS?

Lars Krogsveen is registered as general manager of KOLVIK & KROGSVEEN AS.

Where is KOLVIK & KROGSVEEN AS based?

KOLVIK & KROGSVEEN AS has its business address in Lillehammer.

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.