BIZTRAC BETA
Auditing

REVISOR LARS KLYVE AS

Org. no. 920035809 Limited company (AS) Voss Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 133,000
Equity NOK 260,000
Incorporated 2017
Share capital NOK 55,000

REVISOR LARS KLYVE AS is registered as a limited company in Voss, Vestland with organisation number 920035809. The business is classified under auditing (NACE 69.201). The company was incorporated in 2017. Registered share capital is NOK 55,000, divided into 55000 shares. The company's stated purpose is: “Driva lovbestemt revisjon, rådgjeving, og konsulentverksemd, føra rekneskap for andre, økonomi, skatt, avgift og anna verksemd som naturleg høyrer til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 133,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 133,000
Equity
NOK 260,000
Est. value
NOK 807,000

Financial health · 2025

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

Who owns REVISOR LARS KLYVE AS?

KLYVE HOLDING AS
REVISOR LARS KLYVE AS
NOK 1.5m rev. · NOK 133,000 profit

REVISOR LARS KLYVE AS has 2 registered shareholders:

All shareholders and roles →

Group structure

REVISOR LARS KLYVE AS er morselskap for 1 datterselskap:

Frequently asked questions about REVISOR LARS KLYVE AS

Who owns REVISOR LARS KLYVE AS?

KLYVE HOLDING AS is the largest registered owner, with 99.5%.

What is the revenue of REVISOR LARS KLYVE AS?

REVISOR LARS KLYVE AS had revenue of NOK 1.5m in 2025.

Who is the general manager of REVISOR LARS KLYVE AS?

Lars Klyve is registered as general manager of REVISOR LARS KLYVE AS.

Where is REVISOR LARS KLYVE AS based?

REVISOR LARS KLYVE AS has its business address in Voss.

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.