BIZTRAC BETA
Activities of fitness centres

AMBASSADEN TRENING AS

Org. no. 928835731 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 7.2m
Operating profit NOK −6.9m
Equity NOK 8.4m
Incorporated 2022
Employees 6
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6,9 mill kr).

AMBASSADEN TRENING AS is registered as a limited company in Oslo, Oslo with organisation number 928835731. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 2022 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drifte treningssentre, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.2m in revenue and NOK −6.9m in operating profit.

Key figures · 2024

Revenue
NOK 7.2m
Operating profit
NOK −6.9m
Equity
NOK 8.4m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns AMBASSADEN TRENING AS?

FREDENSBORG AS
AMBASSADEN TRENING AS
NOK 7.2m rev. · NOK −6.9m profit

AMBASSADEN TRENING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AMBASSADEN TRENING AS

Who owns AMBASSADEN TRENING AS?

FREDENSBORG AS is the largest registered owner, with 100.0%.

What is the revenue of AMBASSADEN TRENING AS?

AMBASSADEN TRENING AS had revenue of NOK 7.2m in 2024.

Who is the general manager of AMBASSADEN TRENING AS?

Ingeborg Vesterås Øveraasen is registered as general manager of AMBASSADEN TRENING AS.

Where is AMBASSADEN TRENING AS based?

AMBASSADEN TRENING AS has its business address in Oslo.

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.