BIZTRAC BETA
COMPANY REGISTER PROFILE
917446377 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

EIGUN AS

Org. no. 917446377 Limited company (AS) Øygarden Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 863,000
Operating profit NOK 476,000
Equity NOK 367,000
Incorporated 2016
Share capital NOK 30,000

EIGUN AS is registered as a limited company in Øygarden, Vestland with organisation number 917446377. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Eie og drifte fast eiendom, samt ha eierinteresser i andre selskaper med tilsvarende virksomhet og alt annet hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 863,000 in revenue and NOK 476,000 in operating profit.

Key figures · 2025

Revenue
NOK 863,000
▼ −18 %
Operating profit
NOK 476,000
▲ +179 %
Equity
NOK 367,000
▼ −33 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
27.13
Very good
Current assets ÷ current liabilities
Profitability
23.0%
Very good
Return on total assets
Solidity
15.6%
Satisfactory
Equity as a share of total capital

Who owns EIGUN AS?

EIGUN AS has 6 registered shareholders:

All shareholders and roles →

Which companies does EIGUN AS own?

EIGUN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EIGUN AS

Who owns EIGUN AS?

MARIN LINK HOLDING AS is the largest registered owner, with 20.0%.

What is the revenue of EIGUN AS?

EIGUN AS had revenue of NOK 863,000 in 2025.

Who is the general manager of EIGUN AS?

Jonny Lokøy is registered as general manager of EIGUN AS.

Where is EIGUN AS based?

EIGUN AS has its business address in Knarrevik.

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

Report a problem

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