BIZTRAC BETA
Other tour operator activities

PARADISREISER AS

Org. no. 988913448 Limited company (AS) Drammen Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 65.8m
Operating profit NOK 5.0m
Equity NOK 5.4m
Incorporated 2005
Employees 5
Share capital NOK 300,000

PARADISREISER AS is registered as a limited company in Drammen, Buskerud with organisation number 988913448. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2005 and has 5 registered employees. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Drive virksomhet innen reiseliv og som turoperatør samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 65.8m in revenue and NOK 5.0m in operating profit.

Key figures · 2025

Revenue
NOK 65.8m
Operating profit
NOK 5.0m
Equity
NOK 5.4m
Est. value
NOK 23.7m

Financial health · 2025

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

Who owns PARADISREISER AS?

GRO ANET HOLME BRASTAD
PARADISREISER AS
NOK 65.8m rev. · NOK 5.0m profit

PARADISREISER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PARADISREISER AS own?

PARADISREISER AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about PARADISREISER AS

Who owns PARADISREISER AS?

GRO ANET HOLME BRASTAD is the largest registered owner, with 100.0%.

What is the revenue of PARADISREISER AS?

PARADISREISER AS had revenue of NOK 65.8m in 2025.

Who is the general manager of PARADISREISER AS?

Gro Anet Holme Brastad is registered as general manager of PARADISREISER AS.

Where is PARADISREISER AS based?

PARADISREISER AS has its business address in Svelvik.

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.