BIZTRAC BETA
Construction of residential and non-residential buildings

GREFSEN VEDLIKEHOLD AS

Org. no. 950902957 Limited company (AS) Ullensaker Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK −1.2m
Equity NOK 1.6m
Incorporated 1988
Employees 5
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).

GREFSEN VEDLIKEHOLD AS is registered as a limited company in Ullensaker, Akershus with organisation number 950902957. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1988 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drive med vedlikeholds-, byggeoppdrag, samt salg av byggevarer og alt som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK −1.2m
Equity
NOK 1.6m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns GREFSEN VEDLIKEHOLD AS?

GREFSEN HOLDING AS
GREFSEN VEDLIKEHOLD AS
NOK 3.3m rev. · NOK −1.2m profit

GREFSEN VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GREFSEN VEDLIKEHOLD AS

Who owns GREFSEN VEDLIKEHOLD AS?

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

What is the revenue of GREFSEN VEDLIKEHOLD AS?

GREFSEN VEDLIKEHOLD AS had revenue of NOK 3.3m in 2024.

Where is GREFSEN VEDLIKEHOLD AS based?

GREFSEN VEDLIKEHOLD AS has its business address in Jessheim.

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.