BIZTRAC BETA
Public relations and communication activities

TRE KAMERATER AS

Org. no. 920981275 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK 5.4m
Incorporated 2018
Share capital NOK 35,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).
  • Nylig endring 2026-02-05 Adresseendring registrert 2026-02-05.

TRE KAMERATER AS is registered as a limited company in Oslo, Oslo with organisation number 920981275. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2018. Registered share capital is NOK 35,000, divided into 100 shares. The company's stated purpose is: “Å delta i andre selskaper enten direkte eller ved aksjer samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 5.4m
Est. value
NOK 6.1m

Financial health · 2025

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

Who owns TRE KAMERATER AS?

GANZO AS
TRE KAMERATER AS
NOK 0 rev. · NOK −17,000 profit

TRE KAMERATER AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TRE KAMERATER AS own?

TRE KAMERATER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TRE KAMERATER AS

Who owns TRE KAMERATER AS?

GANZO AS is the largest registered owner, with 50.0%.

What is the revenue of TRE KAMERATER AS?

TRE KAMERATER AS had revenue of NOK 0 in 2025.

Where is TRE KAMERATER AS based?

TRE KAMERATER 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.