BIZTRAC BETA
Rental and operating of own or leased real estate

STRAUME TEKNOLOGISENTER AS

Org. no. 989235893 Limited company (AS) Øygarden Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 16.7m
Operating profit NOK 2.9m
Equity NOK 107,000
Incorporated 2005
Share capital NOK 412,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 TEKNOLOGISENTER AS is registered as a limited company in Øygarden, Vestland with organisation number 989235893. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 412,000, divided into 20200 shares. The company's stated purpose is: “Å eie, leie ut og drifte fast eiendom, samt det som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.7m in revenue and NOK 2.9m in operating profit.

Key figures · 2024

Revenue
NOK 16.7m
Operating profit
NOK 2.9m
Equity
NOK 107,000
Est. value
NOK 5.7m

Financial health · 2024

Liquidity
1.59
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.1%
Not satisfactory
Equity as a share of total capital

Who owns STRAUME TEKNOLOGISENTER AS?

LIEGRUPPEN EIENDOM AS
STRAUME TEKNOLOGISENTER AS
NOK 16.7m rev. · NOK 2.9m profit

STRAUME TEKNOLOGISENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRAUME TEKNOLOGISENTER AS

Who owns STRAUME TEKNOLOGISENTER AS?

LIEGRUPPEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of STRAUME TEKNOLOGISENTER AS?

STRAUME TEKNOLOGISENTER AS had revenue of NOK 16.7m in 2024.

Where is STRAUME TEKNOLOGISENTER AS based?

STRAUME TEKNOLOGISENTER 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.