BIZTRAC BETA
Development of building projects

GREFSENVEIEN 28 AS

Org. no. 928045439 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 551,000
Operating profit NOK −165,000
Equity NOK −1.6m
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,6 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−165k kr).

GREFSENVEIEN 28 AS is registered as a limited company in Oslo, Oslo with organisation number 928045439. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eiendomsutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 551,000 in revenue and NOK −165,000 in operating profit.

Key figures · 2025

Revenue
NOK 551,000
Operating profit
NOK −165,000
Equity
NOK −1.6m

Financial health · 2025

Liquidity
1.82
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-14.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GREFSENVEIEN 28 AS?

MERIDIUS INVEST AS
GREFSENVEIEN 28 AS
NOK 551,000 rev. · NOK −165,000 profit

GREFSENVEIEN 28 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GREFSENVEIEN 28 AS

Who owns GREFSENVEIEN 28 AS?

MERIDIUS INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of GREFSENVEIEN 28 AS?

GREFSENVEIEN 28 AS had revenue of NOK 551,000 in 2025.

Who is the general manager of GREFSENVEIEN 28 AS?

Christian Brede Moe is registered as general manager of GREFSENVEIEN 28 AS.

Where is GREFSENVEIEN 28 AS based?

GREFSENVEIEN 28 AS has its business address in Oslo.

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.