BIZTRAC BETA
Rental and operating of own or leased real estate

TIMBE AS

Org. no. 988950572 Limited company (AS) Alstahaug Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK −68,000
Equity NOK −650,000
Incorporated 2005
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−650k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−68k kr).

TIMBE AS is registered as a limited company in Alstahaug, Nordland with organisation number 988950572. 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 10000 shares. The company's stated purpose is: “Eie og drive utleie av fast eiendom. Selskapet kan også eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK −68,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK −68,000
Equity
NOK −650,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TIMBE AS?

ELISABETH NEERGAARD BLIX
TIMBE AS
NOK 1.9m rev. · NOK −68,000 profit

TIMBE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TIMBE AS

Who owns TIMBE AS?

ELISABETH NEERGAARD BLIX is the largest registered owner, with 50.0%.

What is the revenue of TIMBE AS?

TIMBE AS had revenue of NOK 1.9m in 2024.

Who is the general manager of TIMBE AS?

Elisabeth Neergaard Blix is registered as general manager of TIMBE AS.

Where is TIMBE AS based?

TIMBE AS has its business address in Sandnessjøen.

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.