BIZTRAC BETA
Other technical consultancy

PERMARINE AS

Org. no. 983333788 Limited company (AS) Nærøysund Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 5.0m
Operating profit NOK 2.2m
Equity NOK 2.1m
Incorporated 2001
Share capital NOK 100,000

PERMARINE AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 983333788. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Engineering/fabrikasjon og salg av mekaniske produkter/komponenter,samt produkter og tjenester som hører naturlig sammen med dette, herunder bl.a. (men ikke begrenset til): 1.Taksering/inspeksjonsvirksomhet. 2.Underleveranser, inkl. kjøp og salg. 3.Konsulentvirksomhet. 4.Utleie av personell i tilknytning til ovenstående.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.0m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 5.0m
Operating profit
NOK 2.2m
Equity
NOK 2.1m
Est. value
NOK 7.8m

Financial health · 2024

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

Who owns PERMARINE AS?

PER OTTO BREIVIK
PERMARINE AS
NOK 5.0m rev. · NOK 2.2m profit

PERMARINE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PERMARINE AS

Who owns PERMARINE AS?

PER OTTO BREIVIK is the largest registered owner, with 100.0%.

What is the revenue of PERMARINE AS?

PERMARINE AS had revenue of NOK 5.0m in 2024.

Who is the general manager of PERMARINE AS?

Per Otto Breivik is registered as general manager of PERMARINE AS.

Where is PERMARINE AS based?

PERMARINE AS has its business address in Foldereid.

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.