BIZTRAC BETA
Intermediation service activities for passenger transportation

EINAST-REISER AS

Org. no. 920633684 Limited company (AS) Voss Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 7,000
Operating profit NOK −796
Equity NOK 1,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

EINAST-REISER AS is registered as a limited company in Voss, Vestland with organisation number 920633684. The business is classified under intermediation service activities for passenger transportation (NACE 52.320). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Arrangering av reiser, konsulentvirksomhet, styrearbeid og lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 7,000 in revenue and NOK −796 in operating profit.

Key figures · 2025

Revenue
NOK 7,000
Operating profit
NOK −796
Equity
NOK 1,000
Est. value
NOK 3,000

Financial health · 2025

Liquidity
3053.00
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns EINAST-REISER AS?

EINAR LARSEN
EINAST-REISER AS
NOK 7,000 rev. · NOK −796 profit

EINAST-REISER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EINAST-REISER AS

Who owns EINAST-REISER AS?

EINAR LARSEN is the largest registered owner, with 50.0%.

What is the revenue of EINAST-REISER AS?

EINAST-REISER AS had revenue of NOK 7,000 in 2025.

Who is the general manager of EINAST-REISER AS?

Einar Larsen is registered as general manager of EINAST-REISER AS.

Where is EINAST-REISER AS based?

EINAST-REISER AS has its business address in Voss.

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

Report a problem

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