BIZTRAC BETA
Rental and operating of own or leased real estate

FJELLSETER AS

Org. no. 998616255 Limited company (AS) Bærum Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −82,000
Equity NOK 25.1m
Incorporated 2012
Share capital NOK 2.4m

Signals

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

FJELLSETER AS is registered as a limited company in Bærum, Akershus with organisation number 998616255. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 2.4m, divided into 47552 shares. The company's stated purpose is: “Investering i verdipapir og eiendom og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −82,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −82,000
Equity
NOK 25.1m
Est. value
NOK 159.6m

Financial health · 2025

Liquidity
4.09
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
85.2%
Very good
Equity as a share of total capital

Who owns FJELLSETER AS?

EINAR SCHULTZ
FJELLSETER AS
NOK 0 rev. · NOK −82,000 profit

FJELLSETER AS has 9 registered shareholders:

All shareholders and roles →

Which companies does FJELLSETER AS own?

FJELLSETER AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about FJELLSETER AS

Who owns FJELLSETER AS?

EINAR SCHULTZ is the largest registered owner, with 25.4%.

What is the revenue of FJELLSETER AS?

FJELLSETER AS had revenue of NOK 0 in 2025.

Who is the general manager of FJELLSETER AS?

Einar Schultz is registered as general manager of FJELLSETER AS.

Where is FJELLSETER AS based?

FJELLSETER AS has its business address in Lysaker.

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.