biztrac. BETA
COMPANY REGISTER PROFILE
912213447 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BREKKEVEIEN 61 AS

Org. no. 912213447 Limited company (AS) Frogn Incorporated 1975 Active
Ownership graph ↗
Operating profit NOK −65,000
Equity NOK 6.3m
Incorporated 1975
Share capital NOK 600,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−65k kr).

BREKKEVEIEN 61 AS is registered as a limited company in Frogn, Akershus with organisation number 912213447. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1975. Registered share capital is NOK 600,000, divided into 200 shares. The company's stated purpose is: “Kjøp, utleie, drift og utvikling av fast eiendom, samt alt som dermed står i forbindelse.”.

Former names: HAAHEIM OG BRYNHILDSEN AS, HAAHEIM & BRYNILDSEN AS

Key figures · 2025

Operating profit
NOK −65,000
▼ −8 %
Equity
NOK 6.3m
▲ +9 %
Est. value
NOK 5.8m

Financial health · 2025

Liquidity
27.33
Very good
Current assets ÷ current liabilities
Profitability
0.2%
Not satisfactory
Return on total assets
Solidity
16.9%
Satisfactory
Equity as a share of total capital

Who owns BREKKEVEIEN 61 AS?

BREKKEVEIEN 61 AS
· NOK −65,000 profit

BREKKEVEIEN 61 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BREKKEVEIEN 61 AS own?

BREKKEVEIEN 61 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BREKKEVEIEN 61 AS

Who owns BREKKEVEIEN 61 AS?

O H SLÅKE INVEST AS is the largest registered owner, with 100.0%.

Who is the general manager of BREKKEVEIEN 61 AS?

Richard Slåke is registered as general manager of BREKKEVEIEN 61 AS.

Where is BREKKEVEIEN 61 AS based?

BREKKEVEIEN 61 AS has its business address in Drøbak.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.