BIZTRAC BETA
Manufacture of other food products n.e.c.

TUNISEA AS

Org. no. 936277241 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 125,000
Operating profit NOK −19,000
Equity NOK 7,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-09-15.

TUNISEA AS is registered as a limited company in Trondheim, Trøndelag with organisation number 936277241. The business is classified under manufacture of other food products n.e.c. (NACE 10.890). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling, produksjon og salg av varer innen mat- og næringsmiddelbransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 125,000 in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 125,000
Operating profit
NOK −19,000
Equity
NOK 7,000
Est. value
NOK 71,000

Financial health · 2025

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.7%
Weak
Equity as a share of total capital

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

Who owns TUNISEA AS?

PSO HOLDING AS
TUNISEA AS
NOK 125,000 rev. · NOK −19,000 profit

TUNISEA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TUNISEA AS

Who owns TUNISEA AS?

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

What is the revenue of TUNISEA AS?

TUNISEA AS had revenue of NOK 125,000 in 2025.

Who is the general manager of TUNISEA AS?

Pernille Stokdal Opheim is registered as general manager of TUNISEA AS.

Where is TUNISEA AS based?

TUNISEA AS has its business address in Trondheim.

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.