BIZTRAC BETA
Accounting and bookkeeping

GRIMSTAD REGNSKAP AS

Org. no. 930777404 Limited company (AS) Grimstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 596,000
Equity NOK 104,000
Incorporated 2023
Share capital NOK 30,000

GRIMSTAD REGNSKAP AS is registered as a limited company in Grimstad, Agder with organisation number 930777404. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Yte regnskapsføring og bedriftsøkonomisk rådgivning og det som naturlig hører sammen med dette. Selskapet kan også investere i aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 596,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 596,000
Equity
NOK 104,000
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.4%
Good
Equity as a share of total capital

Who owns GRIMSTAD REGNSKAP AS?

TOUND INVEST AS
GRIMSTAD REGNSKAP AS
NOK 2.0m rev. · NOK 596,000 profit

GRIMSTAD REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GRIMSTAD REGNSKAP AS er morselskap for 1 datterselskap:

Frequently asked questions about GRIMSTAD REGNSKAP AS

Who owns GRIMSTAD REGNSKAP AS?

TOUND INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of GRIMSTAD REGNSKAP AS?

GRIMSTAD REGNSKAP AS had revenue of NOK 2.0m in 2025.

Who is the general manager of GRIMSTAD REGNSKAP AS?

Tor Arnulf Undhjem is registered as general manager of GRIMSTAD REGNSKAP AS.

Where is GRIMSTAD REGNSKAP AS based?

GRIMSTAD REGNSKAP AS has its business address in Grimstad.

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.