BIZTRAC BETA
Rental and operating of own or leased real estate

DIREKTØR HAUGES VEI 1 AS

Org. no. 936758215 Limited company (AS) Fredrikstad Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 974,000
Equity NOK 281,000
Incorporated 2025
Share capital NOK 146,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-10-04.

DIREKTØR HAUGES VEI 1 AS is registered as a limited company in Fredrikstad, Østfold with organisation number 936758215. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 146,000, divided into 30000 shares. The company's stated purpose is: “Utleie av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 974,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 974,000
Equity
NOK 281,000
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns DIREKTØR HAUGES VEI 1 AS?

MÅKEKOLLEN HOLDING AS
DIREKTØR HAUGES VEI 1 AS
NOK 1.1m rev. · NOK 974,000 profit

DIREKTØR HAUGES VEI 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DIREKTØR HAUGES VEI 1 AS

Who owns DIREKTØR HAUGES VEI 1 AS?

MÅKEKOLLEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of DIREKTØR HAUGES VEI 1 AS?

DIREKTØR HAUGES VEI 1 AS had revenue of NOK 1.1m in 2025.

Who is the general manager of DIREKTØR HAUGES VEI 1 AS?

Geir Inge Paulsen is registered as general manager of DIREKTØR HAUGES VEI 1 AS.

Where is DIREKTØR HAUGES VEI 1 AS based?

DIREKTØR HAUGES VEI 1 AS has its business address in Kråkerøy.

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.