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

O. TUFTA A/S

Org. no. 947673939 Limited company (AS) Kvam Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 11.8m
Operating profit NOK −363,000
Equity NOK 3.6m
Incorporated 1988
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−363k kr).

O. TUFTA A/S is registered as a limited company in Kvam, Vestland with organisation number 947673939. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 1988. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Handel med dagligvarer.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.8m in revenue and NOK −363,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.8m
Operating profit
NOK −363,000
Equity
NOK 3.6m
Est. value
NOK 5.6m

Financial health · 2024

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

Who owns O. TUFTA A/S?

ARNE INGEMAR TUFTA
O. TUFTA A/S
NOK 11.8m rev. · NOK −363,000 profit

O. TUFTA A/S has 5 registered shareholders:

All shareholders and roles →

Which companies does O. TUFTA A/S own?

O. TUFTA A/S holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about O. TUFTA A/S

Who owns O. TUFTA A/S?

ARNE INGEMAR TUFTA is the largest registered owner, with 50.0%.

What is the revenue of O. TUFTA A/S?

O. TUFTA A/S had revenue of NOK 11.8m in 2024.

Who is the general manager of O. TUFTA A/S?

Nina Merete Tufta is registered as general manager of O. TUFTA A/S.

Where is O. TUFTA A/S based?

O. TUFTA A/S has its business address in Omastrand.

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.