biztrac. BETA
COMPANY REGISTER PROFILE
913454847 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

YGT3 AS

Org. no. 913454847 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 22.1m
Operating profit NOK −6.9m
Equity NOK 53,000
Incorporated 2014
Employees 25
Share capital NOK 30,000

Signals

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

YGT3 AS is registered as a limited company in Oslo, Oslo with organisation number 913454847. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2014 and has 25 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av restauranter og cafeer.”. The most recent filed accounts, for the 2025 financial year, show NOK 22.1m in revenue and NOK −6.9m in operating profit.

Former names: OSLO FJORD FESTIVAL AS

Key figures · 2025

Revenue
NOK 22.1m
▼ −40 %
Operating profit
NOK −6.9m
▼ −319 %
Equity
NOK 53,000
▼ −98 %
Est. value
NOK 15.4m

Financial health · 2025

Liquidity
0.54
Weak
Current assets ÷ current liabilities
Profitability
-47.6%
Not satisfactory
Return on total assets
Solidity
0.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns YGT3 AS?

YGT3 AS
NOK 22.1m rev. · NOK −6.9m profit

YGT3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about YGT3 AS

Who owns YGT3 AS?

KULTURHUSET I OSLO AS is the largest registered owner, with 100.0%.

What is the revenue of YGT3 AS?

YGT3 AS had revenue of NOK 22.1m in 2025.

Who is the general manager of YGT3 AS?

Karl-Henning Fahlstrøm Svendsen is registered as general manager of YGT3 AS.

Where is YGT3 AS based?

YGT3 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.