BIZTRAC BETA
COMPANY REGISTER PROFILE
813646722 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Buying and selling of own real estate

TJENESTEN AS

Org. no. 813646722 Limited company (AS) Elverum Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 3,000
Operating profit NOK −137,000
Equity NOK 195,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−137k kr).

TJENESTEN AS is registered as a limited company in Elverum, Innlandet with organisation number 813646722. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg innen bygg- og anlegg, skog og hage. Deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 3,000 in revenue and NOK −137,000 in operating profit.

Key figures · 2024

Revenue
NOK 3,000
Operating profit
NOK −137,000
Equity
NOK 195,000
Est. value
NOK 138,000

Financial health · 2024

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

Who owns TJENESTEN AS?

TROND BERTIL AASETH
TJENESTEN AS
NOK 3,000 rev. · NOK −137,000 profit

TJENESTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TJENESTEN AS

Who owns TJENESTEN AS?

TROND BERTIL AASETH is the largest registered owner, with 100.0%.

What is the revenue of TJENESTEN AS?

TJENESTEN AS had revenue of NOK 3,000 in 2024.

Who is the general manager of TJENESTEN AS?

Trond Bertil Aaseth is registered as general manager of TJENESTEN AS.

Where is TJENESTEN AS based?

TJENESTEN AS has its business address in Elverum.

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.