biztrac. BETA
COMPANY REGISTER PROFILE
959557721 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SENN GAVAS AS

Org. no. 959557721 Limited company (AS) Stryn Incorporated 1990 Active
Revenue 2025 NOK 0
Operating profit NOK −70,000
Equity NOK 8.1m
Incorporated 1990
Share capital NOK 2.7m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−70k kr).

SENN GAVAS AS is registered as a limited company in Stryn, Vestland with organisation number 959557721. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1990. Registered share capital is NOK 2.7m, divided into 400 shares. The company's stated purpose is: “Forretningsvirksomhet innan engros og det som står i samband med dette, medrekna å ta del i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −70,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −70,000
▼ −283 %
Equity
NOK 8.1m
▲ +9 %
Est. value
NOK 8.1m

Financial health · 2025

Liquidity
191.91
Very good
Current assets ÷ current liabilities
Profitability
8.9%
Satisfactory
Return on total assets
Solidity
95.6%
Very good
Equity as a share of total capital

Who owns SENN GAVAS AS?

SENN GAVAS AS
NOK 0 rev. · NOK −70,000 profit

SENN GAVAS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SENN GAVAS AS own?

SENN GAVAS AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SENN GAVAS AS

Who owns SENN GAVAS AS?

Arve Glomnes is the largest registered owner, with 100.0%.

What is the revenue of SENN GAVAS AS?

SENN GAVAS AS had revenue of NOK 0 in 2025.

Where is SENN GAVAS AS based?

SENN GAVAS AS has its business address in Stryn.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.