BIZTRAC BETA
Manufacture of prepared meals and dishes

TOVES TRADISJONSMAT AS

Org. no. 929108647 Limited company (AS) Tromsø Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 305,000
Equity NOK 395,000
Incorporated 2022
Employees 8
Share capital NOK 30,000

TOVES TRADISJONSMAT AS is registered as a limited company in Tromsø, Troms with organisation number 929108647. The business is classified under manufacture of prepared meals and dishes (NACE 10.850). The company was incorporated in 2022 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Produksjon og salg av tradisjonsmat samt salg av urtebaserte hudpleieprodukter og kosttilskudd. Kursvirksomhet og enkel servering.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 305,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 305,000
Equity
NOK 395,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns TOVES TRADISJONSMAT AS?

TOVE SELJEVOLD
TOVES TRADISJONSMAT AS
NOK 2.7m rev. · NOK 305,000 profit

TOVES TRADISJONSMAT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOVES TRADISJONSMAT AS

Who owns TOVES TRADISJONSMAT AS?

TOVE SELJEVOLD is the largest registered owner, with 100.0%.

What is the revenue of TOVES TRADISJONSMAT AS?

TOVES TRADISJONSMAT AS had revenue of NOK 2.7m in 2025.

Who is the general manager of TOVES TRADISJONSMAT AS?

Tove Seljevold is registered as general manager of TOVES TRADISJONSMAT AS.

Where is TOVES TRADISJONSMAT AS based?

TOVES TRADISJONSMAT AS has its business address in Vikran.

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.