biztrac. BETA
COMPANY REGISTER PROFILE
991392750 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

JARLE MOJAREN AS

Org. no. 991392750 Limited company (AS) Flesberg Incorporated 2007 Active
Revenue 2025 NOK 429,000
Operating profit NOK 79,000
Equity NOK 689,000
Incorporated 2007
Share capital NOK 100,000

JARLE MOJAREN AS is registered as a limited company in Flesberg, Buskerud with organisation number 991392750. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Godstransport på vei. Brøyting, strøing og annen transportvirksomhet. Brukthandel. Annen virksomhet i tilknytning til dette, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 429,000 in revenue and NOK 79,000 in operating profit.

Key figures · 2025

Revenue
NOK 429,000
▼ −20 %
Operating profit
NOK 79,000
▲ +80 %
Equity
NOK 689,000
▲ +13 %
Est. value
NOK 630,000

Financial health · 2025

Liquidity
27.69
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
96.4%
Very good
Equity as a share of total capital

Who owns JARLE MOJAREN AS?

JARLE MOJAREN AS
NOK 429,000 rev. · NOK 79,000 profit

JARLE MOJAREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JARLE MOJAREN AS

Who owns JARLE MOJAREN AS?

Jarle Mojaren is the largest registered owner, with 100.0%.

What is the revenue of JARLE MOJAREN AS?

JARLE MOJAREN AS had revenue of NOK 429,000 in 2025.

Who is the general manager of JARLE MOJAREN AS?

Jarle Mojaren is registered as general manager of JARLE MOJAREN AS.

Where is JARLE MOJAREN AS based?

JARLE MOJAREN AS has its business address in Svene.

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.