BIZTRAC BETA
Rental and operating of own or leased real estate

FJORDBOTN EIENDOM AS

Org. no. 919917016 Limited company (AS) Senja Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 216,000
Operating profit NOK 135,000
Equity NOK 316,000
Incorporated 2017
Share capital NOK 200,000

FJORDBOTN EIENDOM AS is registered as a limited company in Senja, Troms with organisation number 919917016. 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 200,000, divided into 200 shares. The company's stated purpose is: “Kjøp og salg av bygninger og eiendom, utleie av bygninger og annet, samt andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 216,000 in revenue and NOK 135,000 in operating profit.

Key figures · 2025

Revenue
NOK 216,000
Operating profit
NOK 135,000
Equity
NOK 316,000
Est. value
NOK 450,000

Financial health · 2025

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.2%
Good
Equity as a share of total capital

Who owns FJORDBOTN EIENDOM AS?

STEIN GUNNAR ERIKSEN
FJORDBOTN EIENDOM AS
NOK 216,000 rev. · NOK 135,000 profit

FJORDBOTN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FJORDBOTN EIENDOM AS own?

FJORDBOTN EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FJORDBOTN EIENDOM AS

Who owns FJORDBOTN EIENDOM AS?

STEIN GUNNAR ERIKSEN is the largest registered owner, with 50.0%.

What is the revenue of FJORDBOTN EIENDOM AS?

FJORDBOTN EIENDOM AS had revenue of NOK 216,000 in 2025.

Where is FJORDBOTN EIENDOM AS based?

FJORDBOTN EIENDOM AS has its business address in Botnhamn.

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.