BIZTRAC BETA
Accounting and bookkeeping

THON REGNSKAP AS

Org. no. 819787042 Limited company (AS) Nord-Aurdal Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 385,000
Equity NOK 1.1m
Incorporated 2017
Share capital NOK 100,000

THON REGNSKAP AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 819787042. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Salg av regnskaps-, økonomi-, rådgivnings- og administrasjonstjenester, samt andre tjenester som naturlig faller sammen med dette. Virksomheten kan skje både i egen regi og gjennom deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 385,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 385,000
Equity
NOK 1.1m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns THON REGNSKAP AS?

ERLAND THON HOVRUD
THON REGNSKAP AS
NOK 2.8m rev. · NOK 385,000 profit

THON REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about THON REGNSKAP AS

Who owns THON REGNSKAP AS?

ERLAND THON HOVRUD is the largest registered owner, with 100.0%.

What is the revenue of THON REGNSKAP AS?

THON REGNSKAP AS had revenue of NOK 2.8m in 2025.

Who is the general manager of THON REGNSKAP AS?

Erland Thon Hovrud is registered as general manager of THON REGNSKAP AS.

Where is THON REGNSKAP AS based?

THON REGNSKAP AS has its business address in Skrautvål.

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.