BIZTRAC BETA
Rental and operating of own or leased real estate

BORGUND AS

Org. no. 922126402 Limited company (AS) Ålesund Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK −252,000
Incorporated 2018
Share capital NOK 50,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−252k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

BORGUND AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 922126402. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Eie og drifte fast eiendom, herunder å delta i selskaper med slikt formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK −252,000

Financial health · 2025

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

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

Who owns BORGUND AS?

BORGUND PARK AS
BORGUND AS
NOK 0 rev. · NOK −12,000 profit

BORGUND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORGUND AS

Who owns BORGUND AS?

BORGUND PARK AS is the largest registered owner, with 100.0%.

What is the revenue of BORGUND AS?

BORGUND AS had revenue of NOK 0 in 2025.

Who is the general manager of BORGUND AS?

Fredrik Ferdinand Sætre Waage-Rasmussen is registered as general manager of BORGUND AS.

Where is BORGUND AS based?

BORGUND AS has its business address in Ålesund.

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.