BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGKOMPANIET 123 AS

Org. no. 812039342 Limited company (AS) Lillestrøm Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 19.5m
Operating profit NOK 695,000
Equity NOK 4.4m
Incorporated 2013
Employees 20
Share capital NOK 30,000

BYGGKOMPANIET 123 AS is registered as a limited company in Lillestrøm, Akershus with organisation number 812039342. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013 and has 20 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Entreprenørvirksomhet innenfor bygg- og anleggsbransjen, samt annen nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.5m in revenue and NOK 695,000 in operating profit.

Key figures · 2024

Revenue
NOK 19.5m
Operating profit
NOK 695,000
Equity
NOK 4.4m
Est. value
NOK 4.6m

Financial health · 2024

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

Who owns BYGGKOMPANIET 123 AS?

JAROSLAW MOKWINSKI
BYGGKOMPANIET 123 AS
NOK 19.5m rev. · NOK 695,000 profit

BYGGKOMPANIET 123 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGKOMPANIET 123 AS

Who owns BYGGKOMPANIET 123 AS?

JAROSLAW MOKWINSKI is the largest registered owner, with 100.0%.

What is the revenue of BYGGKOMPANIET 123 AS?

BYGGKOMPANIET 123 AS had revenue of NOK 19.5m in 2024.

Who is the general manager of BYGGKOMPANIET 123 AS?

Jaroslaw Mokwinski is registered as general manager of BYGGKOMPANIET 123 AS.

Where is BYGGKOMPANIET 123 AS based?

BYGGKOMPANIET 123 AS has its business address in Blaker.

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.