BIZTRAC BETA
Activities of advertising agencies

TIBE OSLO AS

Org. no. 929150767 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 12.0m
Operating profit NOK 1.3m
Equity NOK 1.2m
Incorporated 2022
Employees 5
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.

TIBE OSLO AS is registered as a limited company in Oslo, Oslo with organisation number 929150767. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2022 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive kommunikasjonsbyrå samt alt som dermed står i forbindelse, herunder deltakelse i andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.0m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 12.0m
Operating profit
NOK 1.3m
Equity
NOK 1.2m
Est. value
NOK 7.1m

Financial health · 2024

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

Who owns TIBE OSLO AS?

MEDIA 1 MOLDE AS
TIBE OSLO AS
NOK 12.0m rev. · NOK 1.3m profit

TIBE OSLO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TIBE OSLO AS

Who owns TIBE OSLO AS?

MEDIA 1 MOLDE AS is the largest registered owner, with 100.0%.

What is the revenue of TIBE OSLO AS?

TIBE OSLO AS had revenue of NOK 12.0m in 2024.

Who is the general manager of TIBE OSLO AS?

Henriette Hotvedt is registered as general manager of TIBE OSLO AS.

Where is TIBE OSLO AS based?

TIBE OSLO 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.