BIZTRAC BETA
Construction of residential and non-residential buildings

AJ BYGG MESTER AS

Org. no. 936085520 Limited company (AS) Lillestrøm Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 523,000
Operating profit NOK 123,000
Equity NOK 126,000
Incorporated 2025
Share capital NOK 30,000

AJ BYGG MESTER AS is registered as a limited company in Lillestrøm, Akershus with organisation number 936085520. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Byggtjenester for privatpersoner og næring. Oppføring av nybygg, tilbygg og rehabilitering av eksisterende bygg og hva hermed står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 523,000 in revenue and NOK 123,000 in operating profit.

Key figures · 2025

Revenue
NOK 523,000
Operating profit
NOK 123,000
Equity
NOK 126,000
Est. value
NOK 413,000

Financial health · 2025

Liquidity
1.86
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.9%
Good
Equity as a share of total capital

Who owns AJ BYGG MESTER AS?

ARVYDAS JANKEVICIUS
AJ BYGG MESTER AS
NOK 523,000 rev. · NOK 123,000 profit

AJ BYGG MESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AJ BYGG MESTER AS

Who owns AJ BYGG MESTER AS?

ARVYDAS JANKEVICIUS is the largest registered owner, with 100.0%.

What is the revenue of AJ BYGG MESTER AS?

AJ BYGG MESTER AS had revenue of NOK 523,000 in 2025.

Who is the general manager of AJ BYGG MESTER AS?

Arvydas Jankevicius is registered as general manager of AJ BYGG MESTER AS.

Where is AJ BYGG MESTER AS based?

AJ BYGG MESTER AS has its business address in Strømmen.

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.