biztrac. BETA
COMPANY REGISTER PROFILE
916739001 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

EVJAHR AS

Org. no. 916739001 Limited company (AS) Lillestrøm Incorporated 2016 Active
Revenue 2025 NOK 13,000
Operating profit NOK −26,000
Equity NOK 70,000
Incorporated 2016
Share capital NOK 31,000

Signals

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

EVJAHR AS is registered as a limited company in Lillestrøm, Akershus with organisation number 916739001. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2016. Registered share capital is NOK 31,000, divided into 300 shares. The company's stated purpose is: “Å investere i andre selskap, aksjer, verdipapirer og eiendom, samt annet som hører naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 13,000 in revenue and NOK −26,000 in operating profit.

Former names: B.A. REGNSKAP AS, AGURKA AS

Key figures · 2025

Revenue
NOK 13,000
▼ −92 %
Operating profit
NOK −26,000
▼ −119 %
Equity
NOK 70,000
▼ −22 %
Est. value
NOK 45,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns EVJAHR AS?

EVJAHR AS
NOK 13,000 rev. · NOK −26,000 profit

EVJAHR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EVJAHR AS

Who owns EVJAHR AS?

Tore Jahren is the largest registered owner, with 100.0%.

What is the revenue of EVJAHR AS?

EVJAHR AS had revenue of NOK 13,000 in 2025.

Who is the general manager of EVJAHR AS?

Tore Jahren is registered as general manager of EVJAHR AS.

Where is EVJAHR AS based?

EVJAHR AS has its business address in Lillestrøm.

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.