biztrac. BETA
COMPANY REGISTER PROFILE
925479950 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Site preparation

EIAN GRAVESERVICE AS

Org. no. 925479950 Limited company (AS) Åfjord Incorporated 2020 Active
Revenue 2025 NOK 3.8m
Operating profit NOK 62,000
Equity NOK 688,000
Incorporated 2020
Share capital NOK 100,000

EIAN GRAVESERVICE AS is registered as a limited company in Åfjord, Trøndelag with organisation number 925479950. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive som maskinentreprenør og dertil naturlig tilhørende aktiviteter, samt deltakelse i annen virksomhet ved aksjekjøp eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 62,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
▲ +18 %
Operating profit
NOK 62,000
▼ −76 %
Equity
NOK 688,000
▲ +4 %
Est. value
NOK 557,000

Financial health · 2025

Liquidity
2.04
Very good
Current assets ÷ current liabilities
Profitability
4.4%
Weak
Return on total assets
Solidity
38.8%
Good
Equity as a share of total capital

Who owns EIAN GRAVESERVICE AS?

EIAN GRAVESERVICE AS
NOK 3.8m rev. · NOK 62,000 profit

EIAN GRAVESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIAN GRAVESERVICE AS

Who owns EIAN GRAVESERVICE AS?

Hallgeir Bernhard Eian is the largest registered owner, with 100.0%.

What is the revenue of EIAN GRAVESERVICE AS?

EIAN GRAVESERVICE AS had revenue of NOK 3.8m in 2025.

Who is the general manager of EIAN GRAVESERVICE AS?

Henrik Lian Eian is registered as general manager of EIAN GRAVESERVICE AS.

Where is EIAN GRAVESERVICE AS based?

EIAN GRAVESERVICE AS has its business address in Roan.

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.