BIZTRAC BETA
Construction of residential and non-residential buildings

AA SMART BYGG AS

Org. no. 919417080 Limited company (AS) Sandefjord Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 5.4m
Operating profit NOK 1.1m
Equity NOK 44,000
Incorporated 2017
Share capital NOK 30,000

AA SMART BYGG AS is registered as a limited company in Sandefjord, Vestfold with organisation number 919417080. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Byggearbeid og renovasjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.4m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 5.4m
Operating profit
NOK 1.1m
Equity
NOK 44,000
Est. value
NOK 3.0m

Financial health · 2024

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

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

Who owns AA SMART BYGG AS?

ARTURAS ANDRIEKUS
AA SMART BYGG AS
NOK 5.4m rev. · NOK 1.1m profit

AA SMART BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AA SMART BYGG AS own?

AA SMART BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AA SMART BYGG AS

Who owns AA SMART BYGG AS?

ARTURAS ANDRIEKUS is the largest registered owner, with 100.0%.

What is the revenue of AA SMART BYGG AS?

AA SMART BYGG AS had revenue of NOK 5.4m in 2024.

Who is the general manager of AA SMART BYGG AS?

Arturas Andriekus is registered as general manager of AA SMART BYGG AS.

Where is AA SMART BYGG AS based?

AA SMART BYGG AS has its business address in Sandefjord.

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.