BIZTRAC BETA
Rental and operating of own or leased real estate

FJELDTVEDT EIENDOM AS

Org. no. 923392629 Limited company (AS) Gloppen Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 295,000
Operating profit NOK 174,000
Equity NOK 91,000
Incorporated 2019
Share capital NOK 30,000

FJELDTVEDT EIENDOM AS is registered as a limited company in Gloppen, Vestland with organisation number 923392629. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utleie, kjøp og salg av eiendom, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 295,000 in revenue and NOK 174,000 in operating profit.

Key figures · 2024

Revenue
NOK 295,000
Operating profit
NOK 174,000
Equity
NOK 91,000
Est. value
NOK 230,000

Financial health · 2024

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

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

Who owns FJELDTVEDT EIENDOM AS?

THOMAS FJELDTVEDT
FJELDTVEDT EIENDOM AS
NOK 295,000 rev. · NOK 174,000 profit

FJELDTVEDT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FJELDTVEDT EIENDOM AS

Who owns FJELDTVEDT EIENDOM AS?

THOMAS FJELDTVEDT is the largest registered owner, with 100.0%.

What is the revenue of FJELDTVEDT EIENDOM AS?

FJELDTVEDT EIENDOM AS had revenue of NOK 295,000 in 2024.

Who is the general manager of FJELDTVEDT EIENDOM AS?

Thomas Fjeldtvedt is registered as general manager of FJELDTVEDT EIENDOM AS.

Where is FJELDTVEDT EIENDOM AS based?

FJELDTVEDT EIENDOM AS has its business address in Sandane.

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.