BIZTRAC BETA
Development of building projects

GRØVLESVINGEN 59 - 81 AS

Org. no. 936702023 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 12.9m
Operating profit NOK 2.2m
Equity NOK 1.3m
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-11-13.

GRØVLESVINGEN 59 - 81 AS is registered as a limited company in Bergen, Vestland with organisation number 936702023. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eiendomsutvikling og investeringsvirksomhet. Selskapet vil eie og investere i aksjer, verdipapirer, eiendom m.m. og ytelser som faller naturlig med dette, herunder ta på seg relevante konsulent og rådgivende oppdrag for andre.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.9m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 12.9m
Operating profit
NOK 2.2m
Equity
NOK 1.3m
Est. value
NOK 5.4m

Financial health · 2025

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

Who owns GRØVLESVINGEN 59 - 81 AS?

G. FOSS EIENDOM AS
GRØVLESVINGEN 59 - 81 AS
NOK 12.9m rev. · NOK 2.2m profit

GRØVLESVINGEN 59 - 81 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRØVLESVINGEN 59 - 81 AS

Who owns GRØVLESVINGEN 59 - 81 AS?

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

What is the revenue of GRØVLESVINGEN 59 - 81 AS?

GRØVLESVINGEN 59 - 81 AS had revenue of NOK 12.9m in 2025.

Where is GRØVLESVINGEN 59 - 81 AS based?

GRØVLESVINGEN 59 - 81 AS has its business address in Nyborg.

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.