BIZTRAC BETA
COMPANY REGISTER PROFILE
989219898 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

KJERSTI THUNSTRØM AS

Org. no. 989219898 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 200,000
Operating profit NOK 123,000
Equity NOK 2.4m
Incorporated 2005
Share capital NOK 100,000

KJERSTI THUNSTRØM AS is registered as a limited company in Bærum, Akershus with organisation number 989219898. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investere i andre selskaper, verdipapirer og fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 200,000 in revenue and NOK 123,000 in operating profit.

Key figures · 2024

Revenue
NOK 200,000
Operating profit
NOK 123,000
Equity
NOK 2.4m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns KJERSTI THUNSTRØM AS?

KJERSTI THUNSTRØM
KJERSTI THUNSTRØM AS
NOK 200,000 rev. · NOK 123,000 profit

KJERSTI THUNSTRØM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJERSTI THUNSTRØM AS

Who owns KJERSTI THUNSTRØM AS?

KJERSTI THUNSTRØM is the largest registered owner, with 100.0%.

What is the revenue of KJERSTI THUNSTRØM AS?

KJERSTI THUNSTRØM AS had revenue of NOK 200,000 in 2024.

Who is the general manager of KJERSTI THUNSTRØM AS?

Kjersti Thunstrøm is registered as general manager of KJERSTI THUNSTRØM AS.

Where is KJERSTI THUNSTRØM AS based?

KJERSTI THUNSTRØM AS has its business address in Stabekk.

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.