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

FRENGEN EIENDOM AS

Org. no. 920149170 Limited company (AS) Indre Fosen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 34,000
Operating profit NOK −162,000
Equity NOK 244,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

FRENGEN EIENDOM AS is registered as a limited company in Indre Fosen, Trøndelag with organisation number 920149170. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Investeringsselskap, herunder investeringer i aksjer, fast eiendom, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 34,000 in revenue and NOK −162,000 in operating profit.

Key figures · 2025

Revenue
NOK 34,000
▼ −60 %
Operating profit
NOK −162,000
▲ +46 %
Equity
NOK 244,000
▼ −41 %
Est. value
NOK 218,000

Financial health · 2025

Liquidity
3.09
Very good
Current assets ÷ current liabilities
Profitability
-40.9%
Not satisfactory
Return on total assets
Solidity
85.2%
Very good
Equity as a share of total capital

Who owns FRENGEN EIENDOM AS?

FRENGEN EIENDOM AS
NOK 34,000 rev. · NOK −162,000 profit

FRENGEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRENGEN EIENDOM AS

Who owns FRENGEN EIENDOM AS?

FOSEN YARD HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FRENGEN EIENDOM AS?

FRENGEN EIENDOM AS had revenue of NOK 34,000 in 2025.

Where is FRENGEN EIENDOM AS based?

FRENGEN EIENDOM AS has its business address in Rissa.

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.