BIZTRAC BETA
Rental and operating of own or leased real estate

GAMARIN AS

Org. no. 894586842 Limited company (AS) Karmøy Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 521,000
Equity NOK 782,000
Incorporated 2009
Share capital NOK 100,000

GAMARIN AS is registered as a limited company in Karmøy, Rogaland with organisation number 894586842. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive som sikkerhetsinspektører, kapitalinvestering, utleievirksomhet, samt å delta i andre nærliggende virksomheter hvor selskapets ansatte eller aksjonærer har den nødvendige kompetanse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK 521,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK 521,000
Equity
NOK 782,000
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
2.26
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
63.9%
Very good
Equity as a share of total capital

Who owns GAMARIN AS?

GEIR AARVIK
GAMARIN AS
NOK 3.6m rev. · NOK 521,000 profit

GAMARIN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GAMARIN AS own?

GAMARIN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GAMARIN AS

Who owns GAMARIN AS?

GEIR AARVIK is the largest registered owner, with 100.0%.

What is the revenue of GAMARIN AS?

GAMARIN AS had revenue of NOK 3.6m in 2025.

Who is the general manager of GAMARIN AS?

Geir Aarvik is registered as general manager of GAMARIN AS.

Where is GAMARIN AS based?

GAMARIN AS has its business address in Karmsund.

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.