BIZTRAC BETA
Development of building projects

G. FOSS UTVIKLING AS

Org. no. 827431982 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 23.1m
Operating profit NOK 2.4m
Equity NOK 2.1m
Incorporated 2021
Employees 13
Share capital NOK 30,000

G. FOSS UTVIKLING AS is registered as a limited company in Bergen, Vestland with organisation number 827431982. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021 and has 13 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Byggefirma som driver med eiendomsutvikling og investeringsvirksomhet. Selskapet vil ta på seg byggeoppdrag, samt 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 2024 financial year, show NOK 23.1m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 23.1m
Operating profit
NOK 2.4m
Equity
NOK 2.1m
Est. value
NOK 6.5m

Financial health · 2024

Liquidity
4.53
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.3%
Satisfactory
Equity as a share of total capital

Who owns G. FOSS UTVIKLING AS?

G. FOSS HOLDING AS
G. FOSS UTVIKLING AS
NOK 23.1m rev. · NOK 2.4m profit

G. FOSS UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about G. FOSS UTVIKLING AS

Who owns G. FOSS UTVIKLING AS?

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

What is the revenue of G. FOSS UTVIKLING AS?

G. FOSS UTVIKLING AS had revenue of NOK 23.1m in 2024.

Where is G. FOSS UTVIKLING AS based?

G. FOSS UTVIKLING 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.