biztrac. BETA
COMPANY REGISTER PROFILE
925786470 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Electrical installation

JOHAN EEK-LARSEN AS

Org. no. 925786470 Limited company (AS) Bergen Incorporated 1977 Active
Revenue 2025 NOK 816,000
Operating profit NOK −106,000
Equity NOK 961,000
Incorporated 1977
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−106k kr).

JOHAN EEK-LARSEN AS is registered as a limited company in Bergen, Vestland with organisation number 925786470. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 1977. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Installasjon og handel og alt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 816,000 in revenue and NOK −106,000 in operating profit.

Key figures · 2025

Revenue
NOK 816,000
▼ −22 %
Operating profit
NOK −106,000
▼ −160 %
Equity
NOK 961,000
▼ −9 %
Est. value
NOK 698,000

Financial health · 2025

Liquidity
3.30
Very good
Current assets ÷ current liabilities
Profitability
-6.2%
Not satisfactory
Return on total assets
Solidity
77.5%
Very good
Equity as a share of total capital

Who owns JOHAN EEK-LARSEN AS?

JOHAN EEK-LARSEN AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about JOHAN EEK-LARSEN AS

Who owns JOHAN EEK-LARSEN AS?

Johan Kristian Eek-Larsen is the largest registered owner, with 51.0%.

What is the revenue of JOHAN EEK-LARSEN AS?

JOHAN EEK-LARSEN AS had revenue of NOK 816,000 in 2025.

Who is the general manager of JOHAN EEK-LARSEN AS?

Johan Kristian Eek-Larsen is registered as general manager of JOHAN EEK-LARSEN AS.

Where is JOHAN EEK-LARSEN AS based?

JOHAN EEK-LARSEN AS has its business address in Bergen.

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.