BIZTRAC BETA
Rental and operating of own or leased real estate

STRAUME NÆRINGSUTLEIE AS

Org. no. 999146880 Limited company (AS) Øygarden Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 2.3m
Equity NOK 1.4m
Incorporated 2012
Share capital NOK 30,000

Signals

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

STRAUME NÆRINGSUTLEIE AS is registered as a limited company in Øygarden, Vestland with organisation number 999146880. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Oppføring, kjøp, salg, drift og utleie av næringslokaler, og dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 2.3m
Equity
NOK 1.4m
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns STRAUME NÆRINGSUTLEIE AS?

ØYGARDEN NÆRINGSEIENDOM AS
STRAUME NÆRINGSUTLEIE AS
NOK 3.0m rev. · NOK 2.3m profit

STRAUME NÆRINGSUTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRAUME NÆRINGSUTLEIE AS

Who owns STRAUME NÆRINGSUTLEIE AS?

ØYGARDEN NÆRINGSEIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of STRAUME NÆRINGSUTLEIE AS?

STRAUME NÆRINGSUTLEIE AS had revenue of NOK 3.0m in 2025.

Where is STRAUME NÆRINGSUTLEIE AS based?

STRAUME NÆRINGSUTLEIE AS has its business address in Straume.

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.