BIZTRAC BETA
Rental and operating of own or leased real estate

HYLKJE NÆRINGSTOMT AS

Org. no. 912883310 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 1.3m
Equity NOK 15.6m
Incorporated 2013
Share capital NOK 75,000

Signals

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

HYLKJE NÆRINGSTOMT AS is registered as a limited company in Bergen, Vestland with organisation number 912883310. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 75,000, divided into 300 shares. The company's stated purpose is: “Næringsdrift, i hovedsak kjøp og salg av fast eiendom og alt hva herved er forbundet, investeringsvirksomhet og deltakelse i andre virksomhter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 1.3m
Equity
NOK 15.6m
Est. value
NOK 13.7m

Financial health · 2025

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

Who owns HYLKJE NÆRINGSTOMT AS?

MIDGARD NORD AS
HYLKJE NÆRINGSTOMT AS
NOK 1.6m rev. · NOK 1.3m profit

HYLKJE NÆRINGSTOMT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HYLKJE NÆRINGSTOMT AS

Who owns HYLKJE NÆRINGSTOMT AS?

MIDGARD NORD AS is the largest registered owner, with 100.0%.

What is the revenue of HYLKJE NÆRINGSTOMT AS?

HYLKJE NÆRINGSTOMT AS had revenue of NOK 1.6m in 2025.

Where is HYLKJE NÆRINGSTOMT AS based?

HYLKJE NÆRINGSTOMT AS has its business address in Bergen.

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.