biztrac. BETA
COMPANY REGISTER PROFILE
931467670 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

AASE BYGG & BETONG AS

Org. no. 931467670 Limited company (AS) Sunnfjord Incorporated 2023 Active
Revenue 2025 NOK 3.2m
Operating profit NOK 98,000
Equity NOK 192,000
Incorporated 2023
Share capital NOK 30,000

AASE BYGG & BETONG AS is registered as a limited company in Sunnfjord, Vestland with organisation number 931467670. 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 100 shares. The company's stated purpose is: “Oppføring av bygninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 98,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
▲ +43 %
Operating profit
NOK 98,000
▼ −41 %
Equity
NOK 192,000
▲ +43 %
Est. value
NOK 357,000

Financial health · 2025

Liquidity
1.32
Satisfactory
Current assets ÷ current liabilities
Profitability
10.1%
Good
Return on total assets
Solidity
20.0%
Good
Equity as a share of total capital

Who owns AASE BYGG & BETONG AS?

AASE BYGG & BETONG AS
NOK 3.2m rev. · NOK 98,000 profit

AASE BYGG & BETONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AASE BYGG & BETONG AS

Who owns AASE BYGG & BETONG AS?

Thomas Aase is the largest registered owner, with 100.0%.

What is the revenue of AASE BYGG & BETONG AS?

AASE BYGG & BETONG AS had revenue of NOK 3.2m in 2025.

Who is the general manager of AASE BYGG & BETONG AS?

Thomas Aase is registered as general manager of AASE BYGG & BETONG AS.

Where is AASE BYGG & BETONG AS based?

AASE BYGG & BETONG AS has its business address in Førde.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.