BIZTRAC BETA
Rental and operating of own or leased real estate

SVINGEN SB AS

Org. no. 994314963 Limited company (AS) Øygarden Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 801,000
Equity NOK 7.8m
Incorporated 2009
Share capital NOK 100,000

Signals

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

SVINGEN SB AS is registered as a limited company in Øygarden, Vestland with organisation number 994314963. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets formål er kjøp og salg av eiendom, prosjektutvikling herunder salg av tomter og bygninger samt å interessere seg i andre foretak og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 801,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 801,000
Equity
NOK 7.8m
Est. value
NOK 7.8m

Financial health · 2025

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

Who owns SVINGEN SB AS?

TELLE GRUPPEN AS
SVINGEN SB AS
NOK 2.0m rev. · NOK 801,000 profit

SVINGEN SB AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SVINGEN SB AS er morselskap for 29 datterselskaper:

Frequently asked questions about SVINGEN SB AS

Who owns SVINGEN SB AS?

TELLE GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of SVINGEN SB AS?

SVINGEN SB AS had revenue of NOK 2.0m in 2025.

Where is SVINGEN SB AS based?

SVINGEN SB AS has its business address in Fjell.

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.