BIZTRAC BETA
Rental and operating of own or leased real estate

LÁIGOVIESUT FANASGIEDDI AS

Org. no. 931769618 Limited company (AS) Tana Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 441,000
Operating profit NOK 174,000
Equity NOK 1.0m
Incorporated 2023
Share capital NOK 1.0m

LÁIGOVIESUT FANASGIEDDI AS is registered as a limited company in Tana, Finnmark with organisation number 931769618. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Utleie av fast eiendom samt virksomhet som står i naturlig forbindelse til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 441,000 in revenue and NOK 174,000 in operating profit.

Key figures · 2024

Revenue
NOK 441,000
Operating profit
NOK 174,000
Equity
NOK 1.0m
Est. value
NOK 978,000

Financial health · 2024

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.1%
Good
Equity as a share of total capital

Who owns LÁIGOVIESUT FANASGIEDDI AS?

ZATTIS BURSA AS
LÁIGOVIESUT FANASGIEDDI AS
NOK 441,000 rev. · NOK 174,000 profit

LÁIGOVIESUT FANASGIEDDI AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LÁIGOVIESUT FANASGIEDDI AS

Who owns LÁIGOVIESUT FANASGIEDDI AS?

ZATTIS BURSA AS is the largest registered owner, with 50.0%.

What is the revenue of LÁIGOVIESUT FANASGIEDDI AS?

LÁIGOVIESUT FANASGIEDDI AS had revenue of NOK 441,000 in 2024.

Who is the general manager of LÁIGOVIESUT FANASGIEDDI AS?

John Trygve Solbakk is registered as general manager of LÁIGOVIESUT FANASGIEDDI AS.

Where is LÁIGOVIESUT FANASGIEDDI AS based?

LÁIGOVIESUT FANASGIEDDI AS has its business address in Tana.

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.