BIZTRAC BETA
Rental and operating of own or leased real estate

MEIERIGÅRDEN KIRKENES AS

Org. no. 998387809 Limited company (AS) Sør-Varanger Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 707,000
Equity NOK 2.6m
Incorporated 2012
Share capital NOK 150,000

MEIERIGÅRDEN KIRKENES AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 998387809. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 150,000, divided into 1500 shares. The company's stated purpose is: “Eiendomsutvikling; utleievirksomhet og salg av tjenester samt aktiviteter som naturlig tilhører dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 707,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 707,000
Equity
NOK 2.6m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns MEIERIGÅRDEN KIRKENES AS?

LINE NILSEN
MEIERIGÅRDEN KIRKENES AS
NOK 1.3m rev. · NOK 707,000 profit

MEIERIGÅRDEN KIRKENES AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about MEIERIGÅRDEN KIRKENES AS

Who owns MEIERIGÅRDEN KIRKENES AS?

LINE NILSEN is the largest registered owner, with 20.0%.

What is the revenue of MEIERIGÅRDEN KIRKENES AS?

MEIERIGÅRDEN KIRKENES AS had revenue of NOK 1.3m in 2025.

Who is the general manager of MEIERIGÅRDEN KIRKENES AS?

Nils Andreas Nilsen is registered as general manager of MEIERIGÅRDEN KIRKENES AS.

Where is MEIERIGÅRDEN KIRKENES AS based?

MEIERIGÅRDEN KIRKENES AS has its business address in Kirkenes.

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.