BIZTRAC BETA
Rental and operating of own or leased real estate

GARNES UTVIKLING AS

Org. no. 996282325 Limited company (AS) Osterøy Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 489,000
Equity NOK 8.1m
Incorporated 2010
Share capital NOK 150,000

Signals

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

GARNES UTVIKLING AS is registered as a limited company in Osterøy, Vestland with organisation number 996282325. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 150,000, divided into 100 shares. The company's stated purpose is: “Erverve, forvalte, utvikle og avhende eiendom og virksomhet i tilknytning til dette. Virksomheten skal skje etter forretningsmessige prinsipper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 489,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 489,000
Equity
NOK 8.1m
Est. value
NOK 7.1m

Financial health · 2025

Liquidity
1.64
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
92.8%
Very good
Equity as a share of total capital

Who owns GARNES UTVIKLING AS?

LONEVÅG BESLAGFABRIKK AS
GARNES UTVIKLING AS
NOK 1.0m rev. · NOK 489,000 profit

GARNES UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GARNES UTVIKLING AS

Who owns GARNES UTVIKLING AS?

LONEVÅG BESLAGFABRIKK AS is the largest registered owner, with 100.0%.

What is the revenue of GARNES UTVIKLING AS?

GARNES UTVIKLING AS had revenue of NOK 1.0m in 2025.

Where is GARNES UTVIKLING AS based?

GARNES UTVIKLING AS has its business address in Lonevåg.

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.