BIZTRAC BETA
COMPANY REGISTER PROFILE
946247081 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

FORRETNING OG EIENDOM AS

Org. no. 946247081 Limited company (AS) Bjørnafjorden Incorporated 1988 Active
Ownership graph ↗
Operating profit NOK −197,000
Equity NOK 8,000
Incorporated 1988
Share capital NOK 34,000

Signals

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

FORRETNING OG EIENDOM AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 946247081. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1988. Registered share capital is NOK 34,000, divided into 4250 shares. The company's stated purpose is: “Kjøp, salg, utleie og drift av fast eiendom, samt alt hva hermed står i forbindelse.”.

Former names: Dan Pedersen Rørleggerforretning A/S

Key figures · 2025

Operating profit
NOK −197,000
▲ +42 %
Equity
NOK 8,000
▼ −94 %
Est. value
NOK 7,000

Financial health · 2025

Liquidity
2.43
Very good
Current assets ÷ current liabilities
Profitability
-8.1%
Not satisfactory
Return on total assets
Solidity
0.5%
Weak
Equity as a share of total capital

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

Who owns FORRETNING OG EIENDOM AS?

FORRETNING OG EIENDOM AS
· NOK −197,000 profit

FORRETNING OG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FORRETNING OG EIENDOM AS

Who owns FORRETNING OG EIENDOM AS?

JOHNNY MARTON PEDERSEN is the largest registered owner, with 100.0%.

Who is the general manager of FORRETNING OG EIENDOM AS?

Andre Marton Pedersen is registered as general manager of FORRETNING OG EIENDOM AS.

Where is FORRETNING OG EIENDOM AS based?

FORRETNING OG EIENDOM AS has its business address in Os.

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

Report a problem

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