BIZTRAC BETA
Rental and operating of own or leased real estate

FUTT AS

Org. no. 991317759 Limited company (AS) Ullensaker Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 694,000
Operating profit NOK −1.1m
Equity NOK 16.2m
Incorporated 2007
Share capital NOK 16.2m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,1 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FUTT AS is registered as a limited company in Ullensaker, Akershus with organisation number 991317759. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 16.2m, divided into 100 shares. The company's stated purpose is: “Eiendomsvirksomhet, investering, utvikling, drift og utleie av fast eiendom, herunder også kjøp og salg av eiendommer.”. The most recent filed accounts, for the 2024 financial year, show NOK 694,000 in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK 694,000
Operating profit
NOK −1.1m
Equity
NOK 16.2m
Est. value
NOK 12.1m

Financial health · 2025

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

Who owns FUTT AS?

TORE KVÆRNER AS
FUTT AS
NOK 694,000 rev. · NOK −1.1m profit

FUTT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FUTT AS

Who owns FUTT AS?

TORE KVÆRNER AS is the largest registered owner, with 100.0%.

What is the revenue of FUTT AS?

FUTT AS had revenue of NOK 694,000 in 2024.

Who is the general manager of FUTT AS?

Tore Kværner is registered as general manager of FUTT AS.

Where is FUTT AS based?

FUTT AS has its business address in Jessheim.

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.