BIZTRAC BETA
Activities of tour guides

LIGHTHOUSE NORWAY AS

Org. no. 930749443 Limited company (AS) Tromsø Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 196,000
Equity NOK 723,000
Incorporated 2023
Share capital NOK 50,000

Signals

1 flags
  • Nylig endring 2026-06-12 Adresseendring registrert 2026-06-12.

LIGHTHOUSE NORWAY AS is registered as a limited company in Tromsø, Troms with organisation number 930749443. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2023. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Å komponere og fasilitere foredrag/kurs og å formidle guider i Norden. Videre skal selskapet investere i aksjer og fond”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 196,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 196,000
Equity
NOK 723,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns LIGHTHOUSE NORWAY AS?

SUSANNE KIRCHBERGER
LIGHTHOUSE NORWAY AS
NOK 1.3m rev. · NOK 196,000 profit

LIGHTHOUSE NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIGHTHOUSE NORWAY AS

Who owns LIGHTHOUSE NORWAY AS?

SUSANNE KIRCHBERGER is the largest registered owner, with 100.0%.

What is the revenue of LIGHTHOUSE NORWAY AS?

LIGHTHOUSE NORWAY AS had revenue of NOK 1.3m in 2025.

Who is the general manager of LIGHTHOUSE NORWAY AS?

Susanne Kirchberger is registered as general manager of LIGHTHOUSE NORWAY AS.

Where is LIGHTHOUSE NORWAY AS based?

LIGHTHOUSE NORWAY AS has its business address in Tromsø.

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.