BIZTRAC BETA
COMPANY REGISTER PROFILE
989177885 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

EINAR LERVIK AS

Org. no. 989177885 Limited company (AS) Heim Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −27,000
Equity NOK 1.8m
Incorporated 2005
Share capital NOK 490,000

Signals

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

EINAR LERVIK AS is registered as a limited company in Heim, Trøndelag with organisation number 989177885. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 490,000, divided into 490 shares. The company's stated purpose is: “Kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −27,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −27,000
▼ −90 %
Equity
NOK 1.8m
▲ +20 %
Est. value
NOK 3.1m

Financial health · 2025

Liquidity
3.84
Very good
Current assets ÷ current liabilities
Profitability
30.8%
Very good
Return on total assets
Solidity
85.4%
Very good
Equity as a share of total capital

Who owns EINAR LERVIK AS?

EINAR LERVIK AS
NOK 0 rev. · NOK −27,000 profit

EINAR LERVIK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EINAR LERVIK AS own?

EINAR LERVIK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EINAR LERVIK AS

Who owns EINAR LERVIK AS?

EINAR LERVIK is the largest registered owner, with 100.0%.

What is the revenue of EINAR LERVIK AS?

EINAR LERVIK AS had revenue of NOK 0 in 2025.

Where is EINAR LERVIK AS based?

EINAR LERVIK AS has its business address in Kyrksæterøra.

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.