BIZTRAC BETA
Construction of residential and non-residential buildings

AUGUSTUS BYGG AS

Org. no. 816613302 Limited company (AS) Holmestrand Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK −34,000
Equity NOK 465,000
Incorporated 2016
Employees 6
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−34k kr).

AUGUSTUS BYGG AS is registered as a limited company in Holmestrand, Vestfold with organisation number 816613302. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Byggearbeid og renovasjon, kjøp og salg av materialer, import og export.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK −34,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
Operating profit
NOK −34,000
Equity
NOK 465,000
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns AUGUSTUS BYGG AS?

AURIMAS BAUZYS
AUGUSTUS BYGG AS
NOK 4.7m rev. · NOK −34,000 profit

AUGUSTUS BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AUGUSTUS BYGG AS

Who owns AUGUSTUS BYGG AS?

AURIMAS BAUZYS is the largest registered owner, with 100.0%.

What is the revenue of AUGUSTUS BYGG AS?

AUGUSTUS BYGG AS had revenue of NOK 4.7m in 2025.

Who is the general manager of AUGUSTUS BYGG AS?

Aurimas Bauzys is registered as general manager of AUGUSTUS BYGG AS.

Where is AUGUSTUS BYGG AS based?

AUGUSTUS BYGG AS has its business address in Eidsfoss.

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.