BIZTRAC BETA
Other real estate activities on a fee or contract basis

BÅTHUSET OPPLAG AS

Org. no. 983603610 Limited company (AS) Kristiansand Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 2.8m
Equity NOK 3.1m
Incorporated 2001
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BÅTHUSET OPPLAG AS is registered as a limited company in Kristiansand, Agder with organisation number 983603610. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie, utvikle og forvalte eiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 2.8m in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 2.8m
Equity
NOK 3.1m
Est. value
NOK 6.3m

Financial health · 2025

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

Who owns BÅTHUSET OPPLAG AS?

BÅTHUSET GRUPPEN AS
BÅTHUSET OPPLAG AS
NOK 4.0m rev. · NOK 2.8m profit

BÅTHUSET OPPLAG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BÅTHUSET OPPLAG AS

Who owns BÅTHUSET OPPLAG AS?

BÅTHUSET GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of BÅTHUSET OPPLAG AS?

BÅTHUSET OPPLAG AS had revenue of NOK 4.0m in 2025.

Who is the general manager of BÅTHUSET OPPLAG AS?

Tore Stray Laastad is registered as general manager of BÅTHUSET OPPLAG AS.

Where is BÅTHUSET OPPLAG AS based?

BÅTHUSET OPPLAG AS has its business address in Kristiansand S.

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.