BIZTRAC BETA
Accounting and bookkeeping

KAUGERUD REGNSKAPSKONTOR AS

Org. no. 914852196 Limited company (AS) Sigdal Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 76,000
Equity NOK 44,000
Incorporated 2015
Share capital NOK 30,000

KAUGERUD REGNSKAPSKONTOR AS is registered as a limited company in Sigdal, Buskerud with organisation number 914852196. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive salg av regnskapsførertjenester, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 76,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 76,000
Equity
NOK 44,000
Est. value
NOK 399,000

Financial health · 2025

Liquidity
1.51
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KAUGERUD REGNSKAPSKONTOR AS?

INGUNN KAUGERUD
KAUGERUD REGNSKAPSKONTOR AS
NOK 1.1m rev. · NOK 76,000 profit

KAUGERUD REGNSKAPSKONTOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KAUGERUD REGNSKAPSKONTOR AS

Who owns KAUGERUD REGNSKAPSKONTOR AS?

INGUNN KAUGERUD is the largest registered owner, with 100.0%.

What is the revenue of KAUGERUD REGNSKAPSKONTOR AS?

KAUGERUD REGNSKAPSKONTOR AS had revenue of NOK 1.1m in 2025.

Who is the general manager of KAUGERUD REGNSKAPSKONTOR AS?

Ingunn Kaugerud is registered as general manager of KAUGERUD REGNSKAPSKONTOR AS.

Where is KAUGERUD REGNSKAPSKONTOR AS based?

KAUGERUD REGNSKAPSKONTOR AS has its business address in Prestfoss.

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.