BIZTRAC BETA
Restaurant activities

TULLINS CAFE AS

Org. no. 913013034 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 16.6m
Operating profit NOK 112,000
Equity NOK 1.4m
Incorporated 2013
Employees 33
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TULLINS CAFE AS is registered as a limited company in Oslo, Oslo with organisation number 913013034. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2013 and has 33 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av restaurant og kafe og all annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.6m in revenue and NOK 112,000 in operating profit.

Key figures · 2024

Revenue
NOK 16.6m
Operating profit
NOK 112,000
Equity
NOK 1.4m
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns TULLINS CAFE AS?

EIENDOM INVEST OSLO AS
TULLINS CAFE AS
NOK 16.6m rev. · NOK 112,000 profit

TULLINS CAFE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TULLINS CAFE AS

Who owns TULLINS CAFE AS?

EIENDOM INVEST OSLO AS is the largest registered owner, with 100.0%.

What is the revenue of TULLINS CAFE AS?

TULLINS CAFE AS had revenue of NOK 16.6m in 2024.

Who is the general manager of TULLINS CAFE AS?

Babar Javed Ali is registered as general manager of TULLINS CAFE AS.

Where is TULLINS CAFE AS based?

TULLINS CAFE 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.