BIZTRAC BETA
Architectural activities

TJÅLIND AS

Org. no. 990668531 Limited company (AS) Time Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK 2.8m
Incorporated 2006
Share capital NOK 100,000

Signals

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

TJÅLIND AS is registered as a limited company in Time, Rogaland with organisation number 990668531. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er investering i verdipapir og eiendom, og alt hva dermed står i forbindelse, samt deltagelse i andre virksomheter av enhver art. ”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 2.8m
Est. value
NOK 4.6m

Financial health · 2024

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

Who owns TJÅLIND AS?

BJØRN MAGNAR TJÅLAND
TJÅLIND AS
NOK 0 rev. · NOK −7,000 profit

TJÅLIND AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TJÅLIND AS own?

TJÅLIND AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TJÅLIND AS

Who owns TJÅLIND AS?

BJØRN MAGNAR TJÅLAND is the largest registered owner, with 50.0%.

What is the revenue of TJÅLIND AS?

TJÅLIND AS had revenue of NOK 0 in 2024.

Who is the general manager of TJÅLIND AS?

Ann Iren Lindland is registered as general manager of TJÅLIND AS.

Where is TJÅLIND AS based?

TJÅLIND AS has its business address in Lye.

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.