BIZTRAC BETA
Construction of residential and non-residential buildings

AASGARD BYGG AS

Org. no. 920317065 Limited company (AS) Skaun Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 12.6m
Operating profit NOK 308,000
Equity NOK 2.3m
Incorporated 2018
Employees 11
Share capital NOK 100,000

AASGARD BYGG AS is registered as a limited company in Skaun, Trøndelag with organisation number 920317065. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tømrertjenester, servicearbeid, renovering og oppføring av bygninger, kjøp og salg av varer som naturlig hører inn under bransjen. Deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.6m in revenue and NOK 308,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.6m
Operating profit
NOK 308,000
Equity
NOK 2.3m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns AASGARD BYGG AS?

ROMUALDAS AFANASJEVAS
AASGARD BYGG AS
NOK 12.6m rev. · NOK 308,000 profit

AASGARD BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AASGARD BYGG AS

Who owns AASGARD BYGG AS?

ROMUALDAS AFANASJEVAS is the largest registered owner, with 100.0%.

What is the revenue of AASGARD BYGG AS?

AASGARD BYGG AS had revenue of NOK 12.6m in 2025.

Who is the general manager of AASGARD BYGG AS?

Romualdas Afanasjevas is registered as general manager of AASGARD BYGG AS.

Where is AASGARD BYGG AS based?

AASGARD BYGG AS has its business address in Børsa.

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.