BIZTRAC BETA
Other real estate activities on a fee or contract basis

DAVIDS BLIDSGATE 3 AS

Org. no. 917418217 Limited company (AS) Indre Østfold Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 294,000
Equity NOK 366,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-06 Adresseendring registrert 2026-02-06.

DAVIDS BLIDSGATE 3 AS is registered as a limited company in Indre Østfold, Østfold with organisation number 917418217. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eiendomsforvaltning og omsorgstjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 294,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 294,000
Equity
NOK 366,000
Est. value
NOK 691,000

Financial health · 2024

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

Who owns DAVIDS BLIDSGATE 3 AS?

KJELL ROBERT MYRVANG
DAVIDS BLIDSGATE 3 AS
NOK 2.0m rev. · NOK 294,000 profit

DAVIDS BLIDSGATE 3 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DAVIDS BLIDSGATE 3 AS

Who owns DAVIDS BLIDSGATE 3 AS?

KJELL ROBERT MYRVANG is the largest registered owner, with 50.0%.

What is the revenue of DAVIDS BLIDSGATE 3 AS?

DAVIDS BLIDSGATE 3 AS had revenue of NOK 2.0m in 2024.

Who is the general manager of DAVIDS BLIDSGATE 3 AS?

Kjell Robert Myrvang is registered as general manager of DAVIDS BLIDSGATE 3 AS.

Where is DAVIDS BLIDSGATE 3 AS based?

DAVIDS BLIDSGATE 3 AS has its business address in Mysen.

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.