BIZTRAC BETA
COMPANY REGISTER PROFILE
979992610 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Marine fishing

TOMMY LENNART AS

Org. no. 979992610 Limited company (AS) Vågan Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 3,000
Operating profit NOK −97,000
Equity NOK 699,000
Incorporated 1998
Share capital NOK 130,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−97k kr).

TOMMY LENNART AS is registered as a limited company in Vågan, Nordland with organisation number 979992610. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 1998. Registered share capital is NOK 130,000, divided into 276 shares. The company's stated purpose is: “Fiskefartøy med tilhørende virksomhet, herunder også å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3,000 in revenue and NOK −97,000 in operating profit.

Key figures · 2025

Revenue
NOK 3,000
▼ −97 %
Operating profit
NOK −97,000
▼ −58 %
Equity
NOK 699,000
▼ −10 %
Est. value
NOK 334,000

Financial health · 2025

Liquidity
73.21
Very good
Current assets ÷ current liabilities
Profitability
-10.6%
Not satisfactory
Return on total assets
Solidity
99.3%
Very good
Equity as a share of total capital

Who owns TOMMY LENNART AS?

TOMMY LENNART AS
NOK 3,000 rev. · NOK −97,000 profit

TOMMY LENNART AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOMMY LENNART AS

Who owns TOMMY LENNART AS?

MAGNE ALBERTSEN is the largest registered owner, with 100.0%.

What is the revenue of TOMMY LENNART AS?

TOMMY LENNART AS had revenue of NOK 3,000 in 2025.

Who is the general manager of TOMMY LENNART AS?

Magne Albertsen is registered as general manager of TOMMY LENNART AS.

Where is TOMMY LENNART AS based?

TOMMY LENNART AS has its business address in Kleppstad.

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.