BIZTRAC BETA
Construction of residential and non-residential buildings

JEVIN BYGG AS

Org. no. 926434462 Limited company (AS) Aurskog-Høland Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK −166,000
Equity NOK 251,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−166k kr).
  • Nylig endring 2026-07-30 Adresseendring registrert 2026-07-30.

JEVIN BYGG AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 926434462. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Snekkerarbeid, anleggsarbeid, og alt som hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −166,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK −166,000
Equity
NOK 251,000
Est. value
NOK 509,000

Financial health · 2024

Liquidity
2.79
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.4%
Good
Equity as a share of total capital

Who owns JEVIN BYGG AS?

JEVGENIJ PEREPIOLKIN
JEVIN BYGG AS
NOK 1.8m rev. · NOK −166,000 profit

JEVIN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JEVIN BYGG AS

Who owns JEVIN BYGG AS?

JEVGENIJ PEREPIOLKIN is the largest registered owner, with 100.0%.

What is the revenue of JEVIN BYGG AS?

JEVIN BYGG AS had revenue of NOK 1.8m in 2025.

Who is the general manager of JEVIN BYGG AS?

Jevgenij Perepiolkin is registered as general manager of JEVIN BYGG AS.

Where is JEVIN BYGG AS based?

JEVIN BYGG AS has its business address in Aurskog.

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.