BIZTRAC BETA
Buying and selling of own real estate

FRYDENLUND STRAND II AS

Org. no. 984806531 Limited company (AS) Sortland Incorporated 2002 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK −268,000
Incorporated 2002
Share capital NOK 100,000

Signals

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

FRYDENLUND STRAND II AS is registered as a limited company in Sortland, Nordland with organisation number 984806531. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Erverve og forvalte eierinteresser i andre selskap, herunder kjøp av fast eiendom.”.

Key figures · 2024

Operating profit
NOK −12,000
Equity
NOK −268,000

Financial health · 2024

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

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

Who owns FRYDENLUND STRAND II AS?

ALV B STEIRO & SØNN AS
FRYDENLUND STRAND II AS
· NOK −12,000 profit

FRYDENLUND STRAND II AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRYDENLUND STRAND II AS own?

FRYDENLUND STRAND II AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FRYDENLUND STRAND II AS

Who owns FRYDENLUND STRAND II AS?

ALV B STEIRO & SØNN AS is the largest registered owner, with 100.0%.

Who is the general manager of FRYDENLUND STRAND II AS?

Rune Steiro is registered as general manager of FRYDENLUND STRAND II AS.

Where is FRYDENLUND STRAND II AS based?

FRYDENLUND STRAND II AS has its business address in Sortland.

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.