BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

JARA BYGG SERVICE AS

Org. no. 931820311 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 687,000
Operating profit NOK 80,000
Equity NOK 12,000
Incorporated 2023
Share capital NOK 30,000

JARA BYGG SERVICE AS is registered as a limited company in Bergen, Vestland with organisation number 931820311. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Import/eksport av diverse varer i forbindelse med byggeprosjekt. Utførende av byggeprosjekt, samt å engasjere seg i andre selskap med liknende formål. Samt kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 687,000 in revenue and NOK 80,000 in operating profit.

Key figures · 2024

Revenue
NOK 687,000
Operating profit
NOK 80,000
Equity
NOK 12,000
Est. value
NOK 260,000

Financial health · 2024

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

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

Who owns JARA BYGG SERVICE AS?

JAROSLAV CHALKOVSKIJ
JARA BYGG SERVICE AS
NOK 687,000 rev. · NOK 80,000 profit

JARA BYGG SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JARA BYGG SERVICE AS

Who owns JARA BYGG SERVICE AS?

JAROSLAV CHALKOVSKIJ is the largest registered owner, with 100.0%.

What is the revenue of JARA BYGG SERVICE AS?

JARA BYGG SERVICE AS had revenue of NOK 687,000 in 2024.

Where is JARA BYGG SERVICE AS based?

JARA BYGG SERVICE AS has its business address in Paradis.

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.