BIZTRAC BETA
Construction of residential and non-residential buildings

AURLAND BYGG AS

Org. no. 930716383 Limited company (AS) Aurland Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −264,000
Equity NOK 240,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−264k kr).

AURLAND BYGG AS is registered as a limited company in Aurland, Vestland with organisation number 930716383. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Entreprenørvirksomhet innen bygg og anlegg, maskinkjøring, investering i andre selskap, eiendomsinvestering, samt kjøp og sal.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −264,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −264,000
Equity
NOK 240,000
Est. value
NOK 818,000

Financial health · 2024

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

Who owns AURLAND BYGG AS?

THOMAS RASTAD
AURLAND BYGG AS
NOK 2.1m rev. · NOK −264,000 profit

AURLAND BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AURLAND BYGG AS

Who owns AURLAND BYGG AS?

THOMAS RASTAD is the largest registered owner, with 100.0%.

What is the revenue of AURLAND BYGG AS?

AURLAND BYGG AS had revenue of NOK 2.1m in 2024.

Who is the general manager of AURLAND BYGG AS?

Thomas Rastad is registered as general manager of AURLAND BYGG AS.

Where is AURLAND BYGG AS based?

AURLAND BYGG AS has its business address in Aurland.

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.