BIZTRAC BETA
Joinery installation

TIDLØST TREVERK AS

Org. no. 929049802 Limited company (AS) Hamar Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 99,000
Operating profit NOK 15,000
Equity NOK −50,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−50k kr).

TIDLØST TREVERK AS is registered as a limited company in Hamar, Innlandet with organisation number 929049802. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Lage interiør og bruksgjenstander av gammelt treverk. Tidløst Treverk AS tar også på seg snekkeroppdrag som nybygg, oppussing og restaureringsarbeid, samt tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 99,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2024

Revenue
NOK 99,000
Operating profit
NOK 15,000
Equity
NOK −50,000
Est. value
NOK 75,000

Financial health · 2024

Liquidity
0.22
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-139.1%
Weak
Equity as a share of total capital

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

Who owns TIDLØST TREVERK AS?

KJETIL REISTAD AASEN
TIDLØST TREVERK AS
NOK 99,000 rev. · NOK 15,000 profit

TIDLØST TREVERK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TIDLØST TREVERK AS

Who owns TIDLØST TREVERK AS?

KJETIL REISTAD AASEN is the largest registered owner, with 50.3%.

What is the revenue of TIDLØST TREVERK AS?

TIDLØST TREVERK AS had revenue of NOK 99,000 in 2024.

Where is TIDLØST TREVERK AS based?

TIDLØST TREVERK AS has its business address in Hamar.

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.