BIZTRAC BETA
Rental and operating of own or leased real estate

SØYLANDSBYGGET AS

Org. no. 915680917 Limited company (AS) Flekkefjord Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 542,000
Equity NOK 911,000
Incorporated 2015
Share capital NOK 900,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SØYLANDSBYGGET AS is registered as a limited company in Flekkefjord, Agder with organisation number 915680917. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 900,000, divided into 900 shares. The company's stated purpose is: “Investering i fast eiendom samt alt hva her hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 542,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 542,000
Equity
NOK 911,000
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns SØYLANDSBYGGET AS?

GUNNAR ÅSLY
SØYLANDSBYGGET AS
NOK 1.7m rev. · NOK 542,000 profit

SØYLANDSBYGGET AS has 3 registered shareholders:

All shareholders and roles →

Which companies does SØYLANDSBYGGET AS own?

SØYLANDSBYGGET AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SØYLANDSBYGGET AS

Who owns SØYLANDSBYGGET AS?

GUNNAR ÅSLY is the largest registered owner, with 33.3%.

What is the revenue of SØYLANDSBYGGET AS?

SØYLANDSBYGGET AS had revenue of NOK 1.7m in 2024.

Where is SØYLANDSBYGGET AS based?

SØYLANDSBYGGET AS has its business address in Flekkefjord.

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.