BIZTRAC BETA
Other tour operator activities

GRIMSTAD SPORTSREISER AS

Org. no. 928309991 Limited company (AS) Grimstad Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 9.7m
Operating profit NOK 372,000
Equity NOK 1.4m
Incorporated 2021
Share capital NOK 500,000

GRIMSTAD SPORTSREISER AS is registered as a limited company in Grimstad, Agder with organisation number 928309991. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2021. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Turoperatør, salg av reiser og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.7m in revenue and NOK 372,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.7m
Operating profit
NOK 372,000
Equity
NOK 1.4m
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns GRIMSTAD SPORTSREISER AS?

SIV BENTE ULVESTAD
GRIMSTAD SPORTSREISER AS
NOK 9.7m rev. · NOK 372,000 profit

GRIMSTAD SPORTSREISER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GRIMSTAD SPORTSREISER AS

Who owns GRIMSTAD SPORTSREISER AS?

SIV BENTE ULVESTAD is the largest registered owner, with 25.5%.

What is the revenue of GRIMSTAD SPORTSREISER AS?

GRIMSTAD SPORTSREISER AS had revenue of NOK 9.7m in 2025.

Where is GRIMSTAD SPORTSREISER AS based?

GRIMSTAD SPORTSREISER 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.