BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

OT DAGLIGVARE AS

Org. no. 936729398 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 501,000
Incorporated 2025
Employees 21
Share capital NOK 500,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-11-23.

OT DAGLIGVARE AS is registered as a limited company in Oslo, Oslo with organisation number 936729398. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2025 and has 21 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”.

Key figures · 2025

Operating profit
NOK −1,000
Equity
NOK 501,000
Est. value
NOK 243,000

Financial health · 2025

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

Who owns OT DAGLIGVARE AS?

RAMI TAHSIN HOLDING AS
OT DAGLIGVARE AS
· NOK −1,000 profit

OT DAGLIGVARE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

OT DAGLIGVARE AS er morselskap for 1 datterselskap:

Frequently asked questions about OT DAGLIGVARE AS

Who owns OT DAGLIGVARE AS?

RAMI TAHSIN HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of OT DAGLIGVARE AS?

Rami Reiersen Tahsin is registered as general manager of OT DAGLIGVARE AS.

Where is OT DAGLIGVARE AS based?

OT DAGLIGVARE 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.