BIZTRAC BETA
Auditing

SIGMUND TOLLERSRUD AS

Org. no. 979647794 Limited company (AS) Hamar Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 879,000
Operating profit NOK 236,000
Equity NOK 519,000
Incorporated 1998
Share capital NOK 30,000

SIGMUND TOLLERSRUD AS is registered as a limited company in Hamar, Innlandet with organisation number 979647794. The business is classified under auditing (NACE 69.201). The company was incorporated in 1998. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tjenesteytende virksomhet innen regnskap, skatt og økonomi, salg av datasystemer, konsulentvirksomhet og annen økonomisk virksomhet som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 879,000 in revenue and NOK 236,000 in operating profit.

Key figures · 2024

Revenue
NOK 879,000
Operating profit
NOK 236,000
Equity
NOK 519,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns SIGMUND TOLLERSRUD AS?

SIGMUND TOLLERSRUD
SIGMUND TOLLERSRUD AS
NOK 879,000 rev. · NOK 236,000 profit

SIGMUND TOLLERSRUD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIGMUND TOLLERSRUD AS

Who owns SIGMUND TOLLERSRUD AS?

SIGMUND TOLLERSRUD is the largest registered owner, with 100.0%.

What is the revenue of SIGMUND TOLLERSRUD AS?

SIGMUND TOLLERSRUD AS had revenue of NOK 879,000 in 2024.

Who is the general manager of SIGMUND TOLLERSRUD AS?

Sigmund Tollersrud is registered as general manager of SIGMUND TOLLERSRUD AS.

Where is SIGMUND TOLLERSRUD AS based?

SIGMUND TOLLERSRUD AS has its business address in Vang På Hedmarken.

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.