BIZTRAC BETA
COMPANY REGISTER PROFILE
999072437 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Support activities for crop production

ERSLAND AS

Org. no. 999072437 Limited company (AS) Vindafjord Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 524,000
Equity NOK 3.2m
Incorporated 2012
Employees 5
Share capital NOK 30,000

ERSLAND AS is registered as a limited company in Vindafjord, Rogaland with organisation number 999072437. The business is classified under support activities for crop production (NACE 01.610). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleige av maskiner og arbeidskraft til bruk i jordbruks- og byggenæringen.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 524,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
▲ +30 %
Operating profit
NOK 524,000
▲ +359 %
Equity
NOK 3.2m
▲ +19 %
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
4.86
Very good
Current assets ÷ current liabilities
Profitability
14.7%
Good
Return on total assets
Solidity
91.1%
Very good
Equity as a share of total capital

Who owns ERSLAND AS?

ERSLAND AS
NOK 1.6m rev. · NOK 524,000 profit

ERSLAND AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERSLAND AS own?

ERSLAND AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ERSLAND AS

Who owns ERSLAND AS?

RUNE ERSLAND is the largest registered owner, with 100.0%.

What is the revenue of ERSLAND AS?

ERSLAND AS had revenue of NOK 1.6m in 2025.

Who is the general manager of ERSLAND AS?

Rune Ersland is registered as general manager of ERSLAND AS.

Where is ERSLAND AS based?

ERSLAND AS has its business address in Skjold.

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.