BIZTRAC BETA
Rental and operating of own or leased real estate

FURULUND SENTER AS

Org. no. 967140031 Limited company (AS) Lillehammer Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 5.5m
Operating profit NOK 2.9m
Equity NOK 4.0m
Incorporated 1993
Share capital NOK 1.0m

FURULUND SENTER AS is registered as a limited company in Lillehammer, Innlandet with organisation number 967140031. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1993. Registered share capital is NOK 1.0m, divided into 5500 shares. The company's stated purpose is: “Eie og forestå drift av forretningseiendommer, samt tilknyttet næringsvirksomhet og annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.5m in revenue and NOK 2.9m in operating profit.

Key figures · 2024

Revenue
NOK 5.5m
Operating profit
NOK 2.9m
Equity
NOK 4.0m
Est. value
NOK 9.6m

Financial health · 2024

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

Who owns FURULUND SENTER AS?

SEIELSTAD HOLDING AS
FURULUND SENTER AS
NOK 5.5m rev. · NOK 2.9m profit

FURULUND SENTER AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FURULUND SENTER AS er morselskap for 5 datterselskaper:

Frequently asked questions about FURULUND SENTER AS

Who owns FURULUND SENTER AS?

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

What is the revenue of FURULUND SENTER AS?

FURULUND SENTER AS had revenue of NOK 5.5m in 2024.

Who is the general manager of FURULUND SENTER AS?

Åge Erling Melbø is registered as general manager of FURULUND SENTER AS.

Where is FURULUND SENTER AS based?

FURULUND SENTER AS has its business address in Lillehammer.

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.