biztrac. BETA
COMPANY REGISTER PROFILE
931375342 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Marine fishing

ROFOSN AS

Org. no. 931375342 Limited company (AS) Harstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 167,000
Operating profit NOK 38,000
Equity NOK 18,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-07 Adresseendring registrert 2026-05-07.

ROFOSN AS is registered as a limited company in Harstad, Troms with organisation number 931375342. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive fiskefartøy samt virksomhet som naturlig hører inn under dette, transport av varer og tjenester, utleie av tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 167,000 in revenue and NOK 38,000 in operating profit.

Key figures · 2025

Revenue
NOK 167,000
▲ +13 %
Operating profit
NOK 38,000
▲ +211 %
Equity
NOK 18,000
▲ +189 %
Est. value
NOK 102,000

Financial health · 2025

Liquidity
5.55
Very good
Current assets ÷ current liabilities
Profitability
7.6%
Satisfactory
Return on total assets
Solidity
3.4%
Weak
Equity as a share of total capital

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

Who owns ROFOSN AS?

ROFOSN AS
NOK 167,000 rev. · NOK 38,000 profit

ROFOSN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROFOSN AS

Who owns ROFOSN AS?

Kristian Hansen is the largest registered owner, with 100.0%.

What is the revenue of ROFOSN AS?

ROFOSN AS had revenue of NOK 167,000 in 2025.

Who is the general manager of ROFOSN AS?

Kristian Hansen is registered as general manager of ROFOSN AS.

Where is ROFOSN AS based?

ROFOSN AS has its business address in Harstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.