BIZTRAC BETA
Rental and operating of own or leased real estate

BERGTUNET NÆRING II AS

Org. no. 919999543 Limited company (AS) Strand Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 230,000
Operating profit NOK −278,000
Equity NOK 264,000
Incorporated 2017
Share capital NOK 90,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−278k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BERGTUNET NÆRING II AS is registered as a limited company in Strand, Rogaland with organisation number 919999543. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 90,000, divided into 30 shares. The company's stated purpose is: “Utvikle eiendom og oppføre bygg, samt tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 230,000 in revenue and NOK −278,000 in operating profit.

Key figures · 2025

Revenue
NOK 230,000
Operating profit
NOK −278,000
Equity
NOK 264,000
Est. value
NOK 241,000

Financial health · 2025

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

Who owns BERGTUNET NÆRING II AS?

STRABO AS
BERGTUNET NÆRING II AS
NOK 230,000 rev. · NOK −278,000 profit

BERGTUNET NÆRING II AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGTUNET NÆRING II AS

Who owns BERGTUNET NÆRING II AS?

STRABO AS is the largest registered owner, with 100.0%.

What is the revenue of BERGTUNET NÆRING II AS?

BERGTUNET NÆRING II AS had revenue of NOK 230,000 in 2025.

Where is BERGTUNET NÆRING II AS based?

BERGTUNET NÆRING II AS has its business address in Tau.

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.