biztrac. BETA
COMPANY REGISTER PROFILE
991871837 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other business support service activities n.e.c.

FERIEBOLIG UTLAND ANS

Org. no. 991871837 General partnership (ANS) Oslo Incorporated 2007 Active
Revenue 2025 NOK 7.3m
Operating profit NOK −104,000
Equity NOK 11.9m
Incorporated 2007

Signals

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

FERIEBOLIG UTLAND ANS is registered as a general partnership in Oslo, Oslo with organisation number 991871837. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 2007. The company's stated purpose is: “Selskapets formål er å eie, drive og utvikle fast eiendom samt forestå formidling av tjenester herunder agenturvirksomhet samt investeringsvirksomhet av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.3m in revenue and NOK −104,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.3m
▲ +23 %
Operating profit
NOK −104,000
▲ +87 %
Equity
NOK 11.9m
▲ +0 %
Est. value
NOK 8.5m

Financial health · 2025

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

Who owns FERIEBOLIG UTLAND ANS?

No shareholders are registered for FERIEBOLIG UTLAND ANS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about FERIEBOLIG UTLAND ANS

What is the revenue of FERIEBOLIG UTLAND ANS?

FERIEBOLIG UTLAND ANS had revenue of NOK 7.3m in 2025.

Who is the general manager of FERIEBOLIG UTLAND ANS?

Sverre Andreas Balteskard is registered as general manager of FERIEBOLIG UTLAND ANS.

Where is FERIEBOLIG UTLAND ANS based?

FERIEBOLIG UTLAND ANS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.