BIZTRAC BETA
Retail sale of fish, crustaceans and molluscs

TOFRE DRIFT AS

Org. no. 997902181 Limited company (AS) Bergen Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 1.9m
Equity NOK −1.4m
Incorporated 2012
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,4 mill kr).

TOFRE DRIFT AS is registered as a limited company in Bergen, Vestland with organisation number 997902181. The business is classified under retail sale of fish, crustaceans and molluscs (NACE 47.230). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av fisk og sjømatprodukter. Selskapet skal i tillegg investere i eiendom og drive med utleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 1.9m
Equity
NOK −1.4m
Est. value
NOK 9.8m

Financial health · 2025

Liquidity
0.07
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1903.3%
Weak
Equity as a share of total capital

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

Who owns TOFRE DRIFT AS?

FISKEBITEN AS
TOFRE DRIFT AS
NOK 2.3m rev. · NOK 1.9m profit

TOFRE DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOFRE DRIFT AS

Who owns TOFRE DRIFT AS?

FISKEBITEN AS is the largest registered owner, with 100.0%.

What is the revenue of TOFRE DRIFT AS?

TOFRE DRIFT AS had revenue of NOK 2.3m in 2025.

Who is the general manager of TOFRE DRIFT AS?

Tom Fredrik Rørnes is registered as general manager of TOFRE DRIFT AS.

Where is TOFRE DRIFT AS based?

TOFRE DRIFT AS has its business address in Mjølkeråen.

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.