BIZTRAC BETA
COMPANY REGISTER PROFILE
998857864 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

LENANGEN BRYGGE AS

Org. no. 998857864 Limited company (AS) Lyngen Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 401,000
Equity NOK 1.2m
Incorporated 2012
Share capital NOK 1.3m

LENANGEN BRYGGE AS is registered as a limited company in Lyngen, Troms with organisation number 998857864. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2012. Registered share capital is NOK 1.3m, divided into 1300 shares. The company's stated purpose is: “Kjøp/salg og utleie av fast eiendom og det som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 401,000 in operating profit.

Former names: LYNGEN MOUNTAIN LODGE AS

Key figures · 2025

Revenue
NOK 1.6m
▼ −2 %
Operating profit
NOK 401,000
▼ −3 %
Equity
NOK 1.2m
▲ +29 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
14.69
Very good
Current assets ÷ current liabilities
Profitability
21.1%
Very good
Return on total assets
Solidity
66.4%
Very good
Equity as a share of total capital

Who owns LENANGEN BRYGGE AS?

LENANGEN BRYGGE AS
NOK 1.6m rev. · NOK 401,000 profit

LENANGEN BRYGGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LENANGEN BRYGGE AS

Who owns LENANGEN BRYGGE AS?

ØRAFISK AS is the largest registered owner, with 100.0%.

What is the revenue of LENANGEN BRYGGE AS?

LENANGEN BRYGGE AS had revenue of NOK 1.6m in 2025.

Who is the general manager of LENANGEN BRYGGE AS?

Per Halvard Hansen is registered as general manager of LENANGEN BRYGGE AS.

Where is LENANGEN BRYGGE AS based?

LENANGEN BRYGGE AS has its business address in Svensby.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.