BIZTRAC BETA
COMPANY REGISTER PROFILE
911581515 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Restaurant activities

BREAKFAST AT TIFFANYS AS

Org. no. 911581515 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 32.8m
Operating profit NOK 4.1m
Equity NOK 9.5m
Incorporated 2013
Employees 34
Share capital NOK 200,000

BREAKFAST AT TIFFANYS AS is registered as a limited company in Oslo, Oslo with organisation number 911581515. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2013 and has 34 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Café og restaurantvirksomhet med servering av mat og drikke og vare som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 32.8m in revenue and NOK 4.1m in operating profit.

Key figures · 2025

Revenue
NOK 32.8m
▲ +4 %
Operating profit
NOK 4.1m
▼ −20 %
Equity
NOK 9.5m
▲ +9 %
Est. value
NOK 21.6m

Financial health · 2025

Liquidity
1.56
Good
Current assets ÷ current liabilities
Profitability
24.0%
Very good
Return on total assets
Solidity
51.4%
Very good
Equity as a share of total capital

Who owns BREAKFAST AT TIFFANYS AS?

BREAKFAST AT TIFFANYS AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BREAKFAST AT TIFFANYS AS

Who owns BREAKFAST AT TIFFANYS AS?

TOKLE AS is the largest registered owner, with 40.0%.

What is the revenue of BREAKFAST AT TIFFANYS AS?

BREAKFAST AT TIFFANYS AS had revenue of NOK 32.8m in 2025.

Who is the general manager of BREAKFAST AT TIFFANYS AS?

Pontus Tobias Dahlström is registered as general manager of BREAKFAST AT TIFFANYS AS.

Where is BREAKFAST AT TIFFANYS AS based?

BREAKFAST AT TIFFANYS 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 02.09.2026.

Report a problem

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