BIZTRAC BETA
Rental and operating of own or leased real estate

FINSTAD UTLEIE AS

Org. no. 932165333 Limited company (AS) Lørenskog Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 256,000
Operating profit NOK 222,000
Equity NOK 212,000
Incorporated 2023
Share capital NOK 30,000

FINSTAD UTLEIE AS is registered as a limited company in Lørenskog, Akershus with organisation number 932165333. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen utleie av eiendom - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 256,000 in revenue and NOK 222,000 in operating profit.

Key figures · 2024

Revenue
NOK 256,000
Operating profit
NOK 222,000
Equity
NOK 212,000
Est. value
NOK 585,000

Financial health · 2024

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

Who owns FINSTAD UTLEIE AS?

FRØKENFIN AS
FINSTAD UTLEIE AS
NOK 256,000 rev. · NOK 222,000 profit

FINSTAD UTLEIE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FINSTAD UTLEIE AS

Who owns FINSTAD UTLEIE AS?

FRØKENFIN AS is the largest registered owner, with 51.0%.

What is the revenue of FINSTAD UTLEIE AS?

FINSTAD UTLEIE AS had revenue of NOK 256,000 in 2024.

Who is the general manager of FINSTAD UTLEIE AS?

Katrine Finstad is registered as general manager of FINSTAD UTLEIE AS.

Where is FINSTAD UTLEIE AS based?

FINSTAD UTLEIE AS has its business address in Finstadjordet.

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.