BIZTRAC BETA
Accounting and bookkeeping

KLEPP REGNSKAP AS

Org. no. 980397599 Limited company (AS) Inderøy Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 16.7m
Operating profit NOK 1.8m
Equity NOK 4.3m
Incorporated 1998
Employees 14
Share capital NOK 75,000

KLEPP REGNSKAP AS is registered as a limited company in Inderøy, Trøndelag with organisation number 980397599. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1998 and has 14 registered employees. Registered share capital is NOK 75,000, divided into 75 shares. The company's stated purpose is: “Tilby tjenester innen regnskapsføring, økonomisk veiledning og annet merkantilt arbeid, samt annen virksomhet som naturlig står i forbindelse med dette. Selskapet kan også gå inn med aksjekapital i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.7m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 16.7m
Operating profit
NOK 1.8m
Equity
NOK 4.3m
Est. value
NOK 11.4m

Financial health · 2024

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

Who owns KLEPP REGNSKAP AS?

RUNDHAUGEN AS
KLEPP REGNSKAP AS
NOK 16.7m rev. · NOK 1.8m profit

KLEPP REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLEPP REGNSKAP AS

Who owns KLEPP REGNSKAP AS?

RUNDHAUGEN AS is the largest registered owner, with 100.0%.

What is the revenue of KLEPP REGNSKAP AS?

KLEPP REGNSKAP AS had revenue of NOK 16.7m in 2024.

Who is the general manager of KLEPP REGNSKAP AS?

Marte Klepp is registered as general manager of KLEPP REGNSKAP AS.

Where is KLEPP REGNSKAP AS based?

KLEPP REGNSKAP AS has its business address in Inderøy.

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.