BIZTRAC BETA
Other technical consultancy

FEARNLEY OFFSHORE SUPPLY VALUATIONS AS

Org. no. 933755525 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

FEARNLEY OFFSHORE SUPPLY VALUATIONS AS is registered as a limited company in Oslo, Oslo with organisation number 933755525. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Rådgivning og konsulenttjenester knyttet til verdsettelse av skip/flåter og skipsrelaterte eiendeler i det maritime markedet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 39,000

Financial health · 2024

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

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

Who owns FEARNLEY OFFSHORE SUPPLY VALUATIONS AS?

FEARNLEY OFFSHORE SUPPLY AS
FEARNLEY OFFSHORE SUPPLY VALUATIONS AS
NOK 0 rev. · NOK 0 profit

FEARNLEY OFFSHORE SUPPLY VALUATIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FEARNLEY OFFSHORE SUPPLY VALUATIONS AS

Who owns FEARNLEY OFFSHORE SUPPLY VALUATIONS AS?

FEARNLEY OFFSHORE SUPPLY AS is the largest registered owner, with 100.0%.

What is the revenue of FEARNLEY OFFSHORE SUPPLY VALUATIONS AS?

FEARNLEY OFFSHORE SUPPLY VALUATIONS AS had revenue of NOK 0 in 2024.

Where is FEARNLEY OFFSHORE SUPPLY VALUATIONS AS based?

FEARNLEY OFFSHORE SUPPLY VALUATIONS AS has its business address in Oslo.

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.